Immich fresh install after update
Hi, I tried updating immich to the latest version this morning but have completely broken my setup.
After re-reading the docus I believe my first mistake was to run "docker-compose pull && docker-compose up -d" instead of "docker compose pull && docker compose up -d". This is because synology is still running the old 20.10.23 docker version.
The update started but before finishing it stopped with the following error:
"permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.project%3Dimmich%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied".
I worked around that using "sudo -E docker-compose pull && sudo -E docker-compose up -d".
Then the update continued but ran into the next issue:
"Error response from daemon: container 5380....33f8e: driver "btrfs" failed to remove root filesystem: Failed to destroy btrfs snapshot /volume2/@docker/btrfs/subvolumes for 269a9d6e11ebe11afa5279ca10890fabd43d6c45024c726d4ba21ea6dad4edf2: invalid argument"
I went out to find the subvolumes folders that were referring to the container and deleted them.
I also went and deleted any images, containers and the entire project, to start setting up immich again. Using my previous .env and .yaml I thought this should not be any issue.
Now to the issue at hand right now: Whenever I now run the docker compose and it's pulling files, it says "8b3... Already exists" and at some point stops with the error: "Error response from daemon: stat /volume2/@docker/btrfs/subvolumes/07e076cd222d36586bbc750f357486997ebfbe6a0b22ebebfd245e35866cc11e: no such file or directory". So immich wants to write to some folders that do not exist anymore and keeps reusing the already downloaded files from earlier even though I have no clue where it gets them from. How can I do a complete new installation of immich?
After re-reading the docus I believe my first mistake was to run "docker-compose pull && docker-compose up -d" instead of "docker compose pull && docker compose up -d". This is because synology is still running the old 20.10.23 docker version.
The update started but before finishing it stopped with the following error:
"permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.project%3Dimmich%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied".
I worked around that using "sudo -E docker-compose pull && sudo -E docker-compose up -d".
Then the update continued but ran into the next issue:
"Error response from daemon: container 5380....33f8e: driver "btrfs" failed to remove root filesystem: Failed to destroy btrfs snapshot /volume2/@docker/btrfs/subvolumes for 269a9d6e11ebe11afa5279ca10890fabd43d6c45024c726d4ba21ea6dad4edf2: invalid argument"
I went out to find the subvolumes folders that were referring to the container and deleted them.
I also went and deleted any images, containers and the entire project, to start setting up immich again. Using my previous .env and .yaml I thought this should not be any issue.
Now to the issue at hand right now: Whenever I now run the docker compose and it's pulling files, it says "8b3... Already exists" and at some point stops with the error: "Error response from daemon: stat /volume2/@docker/btrfs/subvolumes/07e076cd222d36586bbc750f357486997ebfbe6a0b22ebebfd245e35866cc11e: no such file or directory". So immich wants to write to some folders that do not exist anymore and keeps reusing the already downloaded files from earlier even though I have no clue where it gets them from. How can I do a complete new installation of immich?
