Hi guys! I’m going at my first docker attempt…and I’m going in Proxmox. I created an LXC container, from which I installed docker, and portainer. Portainer seems happy to work, and shows its admin page on port 9443 correctly. I tried next running the image of immich, following the steps detailed in their own guide. This…doesn’t seem to open the admin website on port 2283. But then again, it seems to run in its own docker internal network (172.16.0.x). How should I reach immich admin page from another computer in the same network? I’m new to Docker, so I’m not sure how are images supposed to communicate within the normal computer network…Thanks!

  • PunkiBas@lemmy.worldEnglish
    3·
    9 months ago

    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.

    • iturnedintoanewt@lemm.eeOPEnglish
      2·
      9 months ago

      Wow thanks! Let me take a look, I missed the portainer part! Sigh…I followed through the instructions. I deleted the previous stack, and created a new one, this time all the way from portainer. This time I ONLY modified the .env file, well and according to the instructions the .yaml referring to the .env as stack.env now. Made it deploy…and nothing. Still getting the same mkdir error :(

      • PunkiBas@lemmy.worldEnglish
        2·
        9 months ago

        Might be some NFS permissions problem, can you try some other temp directory with say 777 permissions to see if it’s that?

        • iturnedintoanewt@lemm.eeOPEnglish
          1·
          9 months ago

          Thanks! Seems more about how to properly map a local host path/mount on docker. For which I’m completely noob…I think this is where I’m failing right now.