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.

  • aggelalex@lemmy.worldEnglish
    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.

  • yay@lemmy.worldEnglish
    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.

  • Qazwsxedcrfv000@lemmy.unknownsys.comEnglish
    1·
    1 year ago

    I spawned up a LXC in my Proxmox for it as soon as the Reddit fiasco began. Originally tried the Docker way, failed… My Docker is installed the official way by the way. Tried the “install from scratch” way, also failed… Finally gave the source a casual read and decided to compile it from source.

    The pict-rs bit is a hassle. It has taken me some time to get all the dependencies right and compile Imagemagick version 7 for Ubuntu 22.04 from source. But it worked eventually.

    I then installed the rust toolchain and checked out the latest stable release tag at the time aka 0.17.3 and compiled lemmy. Nothing went astray and I followed the remaining steps in the “install from scratch” doc to complete the setup. P.S. Oh right you need to make the lemmy PostgreSQL user SUPERUSER otherwise the database migration script would not work. A commit was already made to make it unnecessary. It will make its way to 0.18.0 release I guess.

    I initially encountered some issues in federation. Subscriptions stuck at pending for remote instances, regardless of their size and traffic. I tried many ways and still it did not work. I have thought of axing the container and restarting from the beginning.

    While I was weighing my options, I found an advice in an issue at lemmy GitHub repo that suggested the problem was leftover from previous hostname changes and dumping the existing database and recreating from sketch would help. I have indeed altered the hostname once or twice during setup. So I followed the advice and federation is working now.

    So far not a butter smooth experience but not the worst I have ever encountered. It does take some troubleshooting capacity and patience. But heck selfhosting has been like that since time immemorial.

  • seang96@spgrn.comEnglish
    1·
    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.worldEnglish
      11·
      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.orgEnglish
        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.

  • ctr1@fl0w.ccEnglish
    1·
    1 year ago

    I was able to get it running from source on Gentoo (without docker). Building from source is an option but you need to manage the dependencies and daemons yourself. This is my first comment! Good luck with your setup

  • TheOneCurly@feddit.online
    0·
    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.