Updating docker-compose database section
I've been using Immich for a couple years so so my docker-compose is a little outdated. I was comparing it to the current example and the database section has changed a decent amount. Can I just replace my current database section with the one from the example or will that cause issues?
My Current:
database:
container_name: immich_postgres
#image: tensorchord/pgvecto-rs:pg14-v0.1.11
image: tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
env_file:
- .env
environment:
POSTGRES_PASSWORD: ${DB_PASSWORD}
POSTGRES_USER: ${DB_USERNAME}
POSTGRES_DB: ${DB_DATABASE_NAME}
volumes:
- pgdata:/var/lib/postgresql/data
restart: always
volumes:
pgdata:
model-cache:7 Replies
:wave: Hey @Todd1561,
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.You can't just replace it, no. If you've kept up with reading the release notes for breaking changes, you should've seen some with instructions for replacing various bits of this. The most critical is the volume mount
I am pretty good about watching the release notes and have made several changes to my docker-compose over time as they've been requested, but I wasn't able to find what release made this switch. And yes, I went back and looked at GitHub, through the commit history and searched past release notes. Do you happen to know what release made this switch?
#8930
thanks, and I just found it myself using different search terms. 🙂 Now that I read this again I remember since it was optional I opted out of making the change. I'll probably still leave it alone and maybe make a note in my compose so I'm not wondering why mine is different from stock in the future.
This thread has been closed. To re-open, use the button below.