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?
4 Replies
:wave: Hey @Florian,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJAChecklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like
fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.GitHub
immich-app immich · Discussions
Explore the GitHub Discussions forum for immich-app immich. Discuss code, ask questions & collaborate with the developer community.
FAQ | Immich
User
GitHub
Issues · immich-app/immich
High performance self-hosted photo and video management solution. - Issues · immich-app/immich
There's something wrong with your docker installation
You could try
docker system prune -a but note that that will wipe out everything docker on your system, so don't do that if you have stuff running that you don't wanna loseI did already do "docker system prune -a --volumes" which does even more than that. I think I have to agree though that something is wrong with my docker and at this point its not necessarily a immich issue anymore.