Has anyone managed to get Lemmy running using Unraid’s docker configuration?

Ive always found the docker part of unraid very clunky for setting up instances outside of the community app plugin. Has anyone managed to get it to work? Did you run into any difficulties?

My current instance is set up on a VPS using the ansible script, but I’d love to move it over to my main server.

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

    binhex hinted that he might be building a CA, other than that people have had luck with docker compose plugin (not me though, can’t get it working)

    • JshKlsn@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Hopefully he does. I want to host my own instance because I hate how every time I join an instance, they decide to block other instances I enjoy. I am sick of hopping around!

    • das@lemellem.dasonic.xyzOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Oh nice, I know the request has been made of Linuxserver as well but I haven’t seen any official response to it

  • shnizmuffin@lemmy.inbutts.lol
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I have one instance mostly* working, but I edited my config/boot/go to install docker-compose. I’m not really using the unRAID UI for anything other than utilization alarms.

    *I’m having issues with postfix email setup, but I’m pretty sure it’s User Error™️.

  • LachlanUnchained@lemmyunchained.net
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    4
    ·
    edit-2
    1 year ago

    Someone asked in a matrix chat ages ago. And I ran it through gpt4 for them. No idea if it worked. Here’s the output.

    Would be interested to see what happens. I don’t use unraid.

    Unraid Docker Installation Guide for Lemmy

    1. Ensure Docker is installed and running on your Unraid server. If not, go to the Unraid web UI, navigate to the ‘Settings’ tab, select ‘Docker’, and set ‘Enable Docker’ to ‘Yes’.

    2. SSH into your Unraid server with a command like ssh root@<YourUnraidServerIP>.

    3. Create a new folder for Lemmy files. The location isn’t important; you can put it anywhere you want. For example: mkdir /mnt/user/appdata/lemmy cd /mnt/user/appdata/lemmy

    4. Download the default config files: wget https://raw.githubusercontent.com/LemmyNet/lemmy/main/docker/docker-compose.yml wget https://raw.githubusercontent.com/LemmyNet/lemmy/main/docker/lemmy.hjson

    5. Set the correct permissions for the ‘pictrs’ folder: mkdir -p volumes/pictrs chown -R 991:991 volumes/pictrs Note: Change the database password in the ‘docker-compose.yml’ file before your first run if you’d like a different one.

    6. Edit the ‘lemmy.hjson’ file, especially the hostname and possibly the db password: nano lemmy.hjson Make necessary adjustments and save the file.

    7. Go to the ‘Docker’ tab in the Unraid web UI. Click ‘Add Container’, put ‘dessalines/lemmy’ in the ‘Repository’ field. In the ‘Config Type’ field, select ‘Path’, then set ‘Container Path’ to ‘/lemmy’ and ‘Host Path’ to ‘/mnt/user/appdata/lemmy’.

    8. Click ‘Apply’ in Unraid to create the Docker container. Unraid will pull down the Docker image and set it up.

    9. You can now access the Lemmy UI at http://<YourUnraidServerIP>:80.

    10. To make Lemmy available outside the server, set up a reverse proxy. In the Unraid ecosystem, this is typically done using a Docker container such as Nginx Proxy Manager or SWAG.

    11. Secure your Lemmy server with TLS, for example with Let’s Encrypt, using your chosen reverse proxy tool.

    Updating Lemmy:

    1. To update Lemmy, go to the ‘Docker’ tab in Unraid, find the ‘Lemmy’ Docker container, and click ‘Check for Updates’. If an update is available, simply click ‘update’ and Unraid will pull down the new Docker image and update your container.

    2. Alternatively, you can manually fetch the latest version from the git repo: wget https://raw.githubusercontent.com/LemmyNet/lemmy/main/docker/docker-compose.yml docker-compose up -d Note: This guide assumes you’re familiar with the basics of using Unraid, such as accessing the web UI, using the terminal, and setting up Docker containers."

    • jon@lemmy.tf
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      These instructions won’t work in anyone’s unraid box, even if they compile compose from source. Not sure why people think posting random chatGPT’d instructions is remotely useful.

      • LachlanUnchained@lemmyunchained.net
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        4
        ·
        1 year ago

        Like I said. Someone in a chat asked me to do it. Was just sharing it here. I don’t use unraid. Just interested if it has any success.

        (Btw. Gpt4 is excellent for this kind of stuff. Have had multitudes of success, and learnt a heap along the way)

        • jon@lemmy.tf
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          Strongly disagree about gpt being excellent for code, it’s extremely confident about the wrong answer most of the time. I’ve found it to be mildly useful as a Stack Overflow alternative (for asking general questions and having it point me in some direction) but it’s code outputs are garbage.

            • jon@lemmy.tf
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              I’ve had access to 4 for several weeks and it’s not really much better. Maybe I’m just asking too much of it though.

              • LachlanUnchained@lemmyunchained.net
                link
                fedilink
                English
                arrow-up
                1
                arrow-down
                1
                ·
                1 year ago

                Generally it will be the user input that causes errors. Like you’re asking the questions the wrong way.

                If you start with trying to debug code, you’ll learn how to utilise it very quickly. It’s an extremely powerful tool.

                Feed it the code. Tell it the behaviour. Tell it the expected behaviour.

                Get it will find the error immediately. For things that would have taken me days to work out previously.