Immich stopped working
I'm very new to docker. I'm only running two containers (Audiobookshelf and immich)
Running on docker desktop 4.40.0
Several changes that may have impacted Immich working
I recently began pruning after updating immich. (docker image prune)
I updated to docker desktop 4.40.0 the day before it happened.
The day after updating immich and docker desktop, I noticed none of m containers were visible in the containers section of docker desktop. I let it be for a couple of days, hoping for the best...
Today I went into powershell and typed docker compose up within the correct directory. Immich started booting bur eventually failed with the following error.
[+] Running 4/5
✔ Network immich_default Created 0.1s
✔ Volume "immich_model-cache" Created 0.0s
- Container immich_postgres Creating 13.4s
✔ Container immich_redis Created 0.5s
✔ Container immich_machine_learning Created 0.4s
error during connect: Post "http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.48/containers/create?name=immich_postgres": EOF
PS C:\Users\dunca\immich-app>
Right before it failed, I had a windows pop up requesting access to the postgress file. I clicked OK.
I'm not sure what to do next. Please help.
See attached env and compose file
6 Replies
:wave: Hey @wired111,
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_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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.This looks like an issue with your docker installation, we recommend using linux for better experience
Thank you. I'm looking into Linux now. Would you recommend using WSL? (Im new to coding, keen to learn and not silly) Will I lose my immich database if I swap over to WSL?
WSL on windows is probably better than docker desktop, you wouldn't do anything if you did a proper backup and restore
Fwiw while switching to Linux is definitely a good move, this issue looks just like an intermittent docker daemon crash that's been going around due to a golang bug. After restarting docker it should carry on fine