• PunkiBas@lemmy.worldEnglish
    2 years

    I have Immich working fine inside an LXC with docker, You just gotta make sure that Keyctl and Nesting are activated in the LXC container’s options in Proxmox and make sure to use the Immich recommended docker-compose file.

    If you still have problems try to take a look at the containers logs with the “docker logs” command to see if there’s an error message somewhere.

      • PunkiBas@lemmy.worldEnglish
        2 years

        That all seems correct, the way to expose services with a docker-compose is by using the:

        ports:
  - 2283:3001

        That means that you expose whatever is at port 3001 in the cointainer (in this case the Immich server inside the docker container, which is exposed by default to 3001) to port 2283 of the host machine (in this case, your LXC container). So it should work if everything else is set up correctly.

        The 172.x.x.x networks are normal internal networks for docker to use, normally you needn’t care about them because you just expose whichever port you need via the ports command above.

        Are you following this step by step to set it all up? is your .env file properly set up? did you check the containers logs?

          • PunkiBas@lemmy.worldEnglish
            2 years

            Ah! now I see the problem

            permission denied, mkdir ‘upload/library’

            It’s clearly having permission problems with the image library directory.

            Also:

            volumes:
 - /mnt/NAS-immich-folder:/mnt/immich
 - ${UPLOAD_LOCATION}:/mnt/immich

            with this command you are trying to mount this directory from your LXC machine:

            /mnt/NAS-immich-folder

            into this directory inside the immich container:

            /mnt/immich

            And then you also try to mount a second directory there in the next line. But immich doesn’t use /mnt/immich for its library, it uses this:

            /usr/src/app/upload

            You should NOT edit the default docker-compose.yml file. Instead you should only edit the .env file like so:

            UPLOAD_LOCATION=/mnt/NAS-immich-folder

            I can also see that there’s a specific tutorial on how to set it up with portainer. In that case you might have to edit the docker compose file to replace .env with stack.env and place the contents of the env file in the advanced-> environment variables of portainer.

            Try these things and ask here again if you can’t get it running.

  • catloaf@lemm.eeEnglish
    2 years

    Wait, you’re running docker inside lxc? I would not do that. I would create a full VM and run docker in there. Or, if that’s all you’re running, skip proxmox and install Debian or whatever on bare metal, and docker on that.

      • chiisana@lemmy.chiisana.netEnglish
        2 years

        Docker inside LXC adds not only the overhead they’d individually add — probably not significant enough for it to matter in a homelab setting — but with it also the added layer of complexity that you’re going to hit when it comes to debugging anything. You’re much better off dropping docker in a full fledged VM instead of running it inside LXC. With a full VM, if nothing else, you can allow the virtual networking to be treated as it’s own separate device on your network, which should reduce a layer of complexity in the problem you’re trying to solve.

        As for your original problem… it sounds like you’re not exposing the docker container layer’s network to your host. Without knowing exactly how you’re launching them (beyond the quirky docker inside LXC setup), it is hard to say where the issue may be. If you’re using compose, try setting the network to external, or bridge, and see if you can expose the service’s port that way. Once you’ve got the port exposure thing figured out, you’re probably better off unexposing the service, setup a proper reverse proxy, and wiring the service to go through your reverse proxy instead.

      • grehund@lemmy.worldEnglish
        2 years

        Jim’s Garage on YT, he recently did a video about running Docker in an LXC. I think you’ll find the info you need there. It can be done, but if you’re new to Docker and/or LXCs, it adds an additional layer of complexity you will have to deal with for every container/stack you deploy.

      • earmuff@lemmy.dbzer0.comEnglish
        2 years

        Add a new VM, install docker-ce on it and slowly migrate all the other containers/vm‘s to docker. End result is way less overhead, way less complexity and way better sleep.

          • earmuff@lemmy.dbzer0.comEnglish
            2 years

            I was assuming you were able to get rid of the other 5 VM‘s by doing so. If not, obviously you would have not less overhead.

              • earmuff@lemmy.dbzer0.comEnglish
                2 years

                My HA is running in docker. It is easier than you might think. Forget about LXC. And just take your time migrating the stuff and only when the service works in docker, you can shut off the VM. Believe me, management of docker is way easier than 5 VM‘s with different OS‘s. Docker Compose is beautiful and easy.

                If you need help, just message me, I might be able to give you a kickstart

      • vzq@lemmy.blahaj.zoneEnglish
        2 years

        You are absolutely free to fuck yourself over by using a niche option plagued by weird problems.

        Or you could, like, not do that.

      • Scrubbles@poptalk.scrubbles.techEnglish
        2 years

        I did it that way for years. It’s not worth the hassle my man. I did the same, told people that it’d be fine, that it was more performant and so it was worth it. But then the problems, oh lord the problems. Every proxmox update brought hours or days of work trying to figure how how it broke this time. Docker updates would make it completely bork. Random freezes, permission errors galore. I threw in the towel on it, figuring I was hacking it making it work anyway.

        Now I do vms on proxmox. Specifically I swapped to k3s which is a whole other thing, but docker in vms runs fine for how much less annoyance there is. Selfhosting became a lot less stressful.

        Learn from our mistakes, OP

  • Avid Amoeba@lemmy.caEnglish
    2 years

    Did you say you’re running docker in LXC? So container in a container? If yes, that’s generally an anti pattern.

  • thirdBreakfast@lemmy.worldEnglish
    2 years

    I routinely run my homelab services as a single Docker inside an LXC - they are quicker, and it makes backups and moving them around trivial. However, while you’re learning, a VM (with something conventional like Debian or Ubuntu) is probably advised - it’s a more common experience so you’ll get more helpful advice when you ask a question like this.

  • Kaavi@lemmy.worldEnglish
    2 years

    I’ve been using proxmox mainly with lxc containers for years. I gave an lxc running docker and portainer, for a few services I have running in docker.

    I wouldn’t do it with anything critical it anything that needs mich performance or resources. But honestly most things don’t need that.

    So is you like me just need a few docker containers and you already have everything else running - this can be a fine way to do it. Go for it :)

  • Decronym@lemmy.decronym.xyzbot accountEnglish
    2 years

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    HA Home Assistant automation software
    ~ High Availability
    HTTP Hypertext Transfer Protocol, the Web
    IP Internet Protocol
    LXC Linux Containers
    NAS Network-Attached Storage
    NFS Network File System, a Unix-based file-sharing protocol known for performance and efficiency
    nginx Popular HTTP server

    6 acronyms in this thread; the most compressed thread commented on today has 6 acronyms.

    [Thread #664 for this sub, first seen 8th Apr 2024, 10:55] [FAQ] [Full list] [Contact] [Source code]

  • N0x0n@lemmy.mlEnglish
    2 years

    Docker networking is fun :) (IMO).

    Without having a look at your container and how you configured it, if you have correctly mapped your ports and didn’t change anything fancy and don’t use a reverse proxy

    Your container should be accessible on your host’s IP mapped with you Immich docker port:

    HostIP:2283

    Edit: Also, don’t run a docker container in… Another container (LXC).

    Containerinception