I’m trying to stand up a Lemmy instance, and for some reason I’m just not getting it. I’ve got a fair bit of experience in Linux and Docker. NPM is new to me, but doesn’t seem difficult.

I’ve looked over several walkthroughs but it seems like they all don’t quite work right. Does someone have a clear step-by-step that works, or could take the time to remote in and help me get this up?

I’m running on VMWare ESXi, and I’ve tried both Debian and Ubuntu to get the server up. Closest I got, the Docker containers would start but seem to be throwing errors internally and don’t connect to one another.

  • mo_ztt ✅@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    I just set it up from a git checkout, and it was pretty involved – the build instructions are actually quite a bit better than usual for development software at this stage, but it’s still a complicated process with some changes vs. what’s in the instructions. If you’re open to that route, I can try to document what I did in more detail + send it along and give some help if you get stuck.

    • giddy@lemmy.perthchat.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Not the OP but I would appreciate it. I got stuck with building the lemmy image. Not sure why they don’t just use a published image

      EDIT - found the problem - the docker compose file has the build options enabled for the lemmy image and the published image commented out

      EDIT 2 - latest issue - 404: FetchError: request to http://lemmy:8536/api/v3/site? failed, reason: getaddrinfo EAI_AGAIN lemmy

      • seang96@exploding-heads.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        I had an AI write 95% of my kurbenetes config. I had this at one point, it is likely you are not proxying (usually nginx) the Lemmy backend to /api and there are are other endpoints that need mapped to it too.