Death Traveller
Explore posts from serversIImmich
•Created by Death Traveller on 12/9/2024 in #help-desk-support
Immich on Docker (Windows 10 WSL2) Failing After Update to v1.122.2
I run Immich on Docker on Windows 10 with WSL2 (Kali Linux integration). A few days ago, I updated Immich from v1.122.1 to v1.122.2. Here's what happened:
Update Process:
- I updated Immich to v1.122.2 post-midnight and restarted the containers using
- Everything worked fine at that time. Next Morning:
- I booted my PC (Docker Desktop is set to start automatically).
- Docker Desktop displayed a message saying "WSL integration failed." This happens occasionally, so I clicked "Restart WSL Integration". Issue:
- Later that day, when I tried to access Immich via
- I attempted restarting the container with
- I checked the logs but couldn’t understand much. After some back-and-forth with ChatGPT, I learned that the issue seems related to the PostgreSQL server.
- The logs mention something like "already exists, skipped initiating" and seem to indicate a connection issue with PostgreSQL.
This issue came up suddenly after the update, and I’ve been stuck for two days trying to fix it. Any advice or guidance would be greatly appreciated!
- I updated Immich to v1.122.2 post-midnight and restarted the containers using
docker-compose up -d.- Everything worked fine at that time. Next Morning:
- I booted my PC (Docker Desktop is set to start automatically).
- Docker Desktop displayed a message saying "WSL integration failed." This happens occasionally, so I clicked "Restart WSL Integration". Issue:
- Later that day, when I tried to access Immich via
localhost:2283 or internal-IP:2283, it didn’t load.- I attempted restarting the container with
docker-compose down and docker-compose up -d, but it still didn’t work.
Debugging Attempts:- I checked the logs but couldn’t understand much. After some back-and-forth with ChatGPT, I learned that the issue seems related to the PostgreSQL server.
- The logs mention something like "already exists, skipped initiating" and seem to indicate a connection issue with PostgreSQL.
This issue came up suddenly after the update, and I’ve been stuck for two days trying to fix it. Any advice or guidance would be greatly appreciated!
68 replies