I
Immich5mo ago
daicon

Help Windows Docker DEsktop - Postgres container restart boot

Hi I can't get the postgres container to run correctly, it is always restarting. I have tried with the windows recommendations to use a new volume ‘pgdata’, and the behaviour is the same. What could be happening? Logs container postgres: 2024-12-28 10:26:39 The files belonging to this database system will be owned by user "postgres". 2024-12-28 10:26:39 This user must also own the server process. 2024-12-28 10:26:39 2024-12-28 10:26:39 The database cluster will be initialized with locale "en_US.utf8". 2024-12-28 10:26:39 The default database encoding has accordingly been set to "UTF8". 2024-12-28 10:26:39 The default text search configuration will be set to "english". 2024-12-28 10:26:39 2024-12-28 10:26:39 Data page checksums are enabled. 2024-12-28 10:26:39 2024-12-28 10:26:39 fixing permissions on existing directory /var/lib/postgresql/data ... ok 2024-12-28 10:26:39 creating subdirectories ... ok 2024-12-28 10:26:39 selecting dynamic shared memory implementation ... posix 2024-12-28 10:26:39 selecting default max_connections ... 100 2024-12-28 10:26:39 selecting default shared_buffers ... 128MB 2024-12-28 10:26:39 selecting default time zone ... Etc/UTC 2024-12-28 10:26:39 creating configuration files ... ok 2024-12-28 10:26:40 running bootstrap script ... ok 2024-12-28 10:26:44 performing post-bootstrap initialization ... ok 2024-12-28 10:26:46 syncing data to disk ... ok 2024-12-28 10:26:46 2024-12-28 10:26:46 2024-12-28 10:26:46 Success. You can now start the database server using: 2024-12-28 10:26:46 2024-12-28 10:26:46 pg_ctl -D /var/lib/postgresql/data -l logfile start 2024-12-28 10:26:46 2024-12-28 10:26:46 waiting for server to start.... stopped waiting 2024-12-28 10:26:48 2024-12-28 10:26:48 PostgreSQL Database directory appears to contain a database; Skipping initialization 2024-12-28 10:26:48 Thanks
2 Replies
Immich
Immich5mo ago
:wave: Hey @daicon, 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.
daicon
daiconOP5mo ago
Logs with option pgdata in env and docker-comsopoe

Did you find this page helpful?