I have tried installing it with docker on Ubuntu 20.04 and 22.04 LTS but cannot seem to get it working. The build keeps erroring out with docker errors.

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

    If your using docker I recommend getting a docker-compose file that does 98% of the config work for you. Pretty sure there’s one in the install docs.

    • TCGM@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      1 year ago

      I’ve been having trouble understanding how the docker-compose thing works, and the whole… impermanence of docker containers. Got any tutorials you’d recommend? Note I’m on Windows.

      • mim@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Are you planning to host it on a Windows machine?

        If you don’t have experience with docker, don’t jump straight to docker compose. Start simpler.

        If you want to have data persist after a container is killed, have a look at the -v option of “docker run”. It allows you to mount a volume.

  • TheOneCurly@feddit.online
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I had some luck with the prebuilt images from dessalines’ dockerhub and using the compose file in the repo with logging commented out.

    It was stable for about a week before I tried to update and broke my database and federation completely. I might try again when 0.18 stable drops.

  • corne@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Will self-hosting Lenny have the limitation that you’ll be missing a lot of comments when subscribing to magazines from other instances? I am considering it tough

    • philipcristiano@lemmy.philipcristiano.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Comments federate to instances with subscribed users for that community. The first time a user subscribes to the community federation will start and future comments will begin to show up on the instance. Can’t see old comments… on smaller/self instances that problem will be more visible.

  • aggelalex@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    You are using two technologies that have a bad of working like shit, together; Ubuntu/snap and docker. You can try podman if you want, or a different distro. Or, at least, install the official docker way.

  • Declared0978@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Been trying for like 2 weeks - Lemmy Easy Deploy, a couple different guides through google, couple different youtube vids, the official docs. In and out of docker, always with a fresh VM (Debian and Ubuntu)… It always installs without errors, but never get it to load the page in a browser. Not sure what’s wrong, maybe just cursed.

  • Lupec@lemmy.lpcha.im
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Not specific to Lemmy but ubuntu’s weird snap version of docker has given me random issues in the past, perhaps that could be the issue. Installing docker by following the official instructions means you are guaranteed to get a fully functional install and that’s one variable you wouldn’t have to worry about at least.

    Edit: Forgot to mention but I’m running it on docker myself, I just followed the official documentation and whatnot. Using a debian 11 based LXC on Proxmox.

  • yay@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I got mine running via Docker by copying the docker-compose, nginx, and lemmy.hjson files from the lemmy-ansible repo. Everything is working so far except votes and comments from other instances. They won’t sync for some reason.

    • jeena@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Here is mine https://gist.github.com/jeena/6179470a8d616455f30635a5c71f5f64 which had a similar problem with the comments, although I couldn’t post comments on my own instance either.

      For me the thing was that I had to add:

      map $http_upgrade $connection_upgrade {
          default upgrade;
          ''      close;
      }
      
      

      and

              proxy_set_header Upgrade $http_upgrade;
              proxy_set_header Connection $connection_upgrade;
      
      

      And also change the nginx in the docker to port 8080 so my normal nginx could keep running on 80 and handle all the ssl certificate stuff.

      My setup is:

      Browser -> native Nginx -> docker Nginx -> lemmy