I
Immich•6d ago
secret

updating immich with dockge, container reset every time

run dockge update button, container reset to start every time, have to restore backup
61 Replies
Immich
Immich•6d ago
:wave: Hey @secret, 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.
Mraedis
Mraedis•6d ago
Looks fine at first glance, let me test something real quick with dockge
secret
secretOP•6d ago
bet heres my dockge compose if necessary
NoMachine
NoMachine•6d ago
I don't know much about dockge, but if I have to guess, it may be related to the use of relative paths UPLOAD_LOCATION=./library DB_DATA_LOCATION=./postgres
secret
secretOP•6d ago
hmm maybe db data location needs to be permanant path?
ahbeng
ahbeng•6d ago
I think so too.. same advice with NoMachine. if the path is not set it thinks its a docker volume and not persistent
Mraedis
Mraedis•6d ago
Probably @NoMachine that's what I was testing 😛
secret
secretOP•6d ago
sounds good hmm
ahbeng
ahbeng•6d ago
it has too... docker volumes if not in defined path will be in docker volumes - that gets wiped out every redeploy
secret
secretOP•6d ago
when i update manually thorugh docker compose pull && docker compose up -d it works fine
ahbeng
ahbeng•6d ago
is it pulling the correct .env file and variables...from dockge? i hardcoded mine at portainer since I don't trust variables and hand-offs with env settings
secret
secretOP•6d ago
hmm thats a valid point lemme check real quick
secret
secretOP•6d ago
No description
secret
secretOP•6d ago
dockge sees the .env file so i think it should pul lthe right things not 100% sure tho
Mraedis
Mraedis•6d ago
Don't put your comment on the same line to be safe 👀
ahbeng
ahbeng•6d ago
yeah... not sure #./portainer mess with it...
secret
secretOP•6d ago
ah yeah that ones new just put that in after everything
Mraedis
Mraedis•6d ago
Are your images also deleted?
secret
secretOP•6d ago
images are fine
Mraedis
Mraedis•6d ago
Because you might want to save that ./library 😛
secret
secretOP•6d ago
i think somethings wrong with db hahaha i have backups on another drive dw
Mraedis
Mraedis•6d ago
It shouldn't present as new if there's something wrong with it It should just never start
secret
secretOP•6d ago
prob postgres location then ive hardcoded it rn to /volume1/docker/immich/postgres lemme hardcode library too and ill wait till next release to test it
ahbeng
ahbeng•6d ago
lol. being paranoid as me... i placed my volume as :ro (my advice)
Mraedis
Mraedis•6d ago
You can't have your UPLOAD_LOCATION be ro
ahbeng
ahbeng•6d ago
ah.. u're right.. i confused it with my external lib i never used upload_location except let immich does it things... ignore me on that
ahbeng
ahbeng•6d ago
hmm.. my portainer compose is pretty old here:
No description
ahbeng
ahbeng•6d ago
is PG_DATA required and @secret secret doesn't have that from what I seen?
secret
secretOP•6d ago
strange seems like I’m missing that I got on around 1.18
ahbeng
ahbeng•6d ago
mine was done since 2023 and hardly updated that part
secret
secretOP•6d ago
lemme check the docs real quick
ahbeng
ahbeng•6d ago
ah.. just crossed checked that part and nope. must by from a residual way way back then
secret
secretOP•6d ago
whoops yeah seems like thats fine
Zeus
Zeus•6d ago
We don’t specify PG_DATA , that’s unnecessary
secret
secretOP•6d ago
theyll prob push a new x.x.1 patch in a few days can prob check that
ahbeng
ahbeng•6d ago
hmm.. i'm so pretty sure that the volumes is not persistent that it missed the env settings. or wrong values from env.. from the your screenshot: /volume1/docker/immich/postgres#./postgres i think it took the #./postgres as part of the value...
secret
secretOP•6d ago
sorry lemme clarify it used to be ./postgres and ./library UPLOAD_LOCATION=/volume1/docker/immich/library #./library The location where your database files are stored DB_DATA_LOCATION=/volume1/docker/immich/postgres ive since changed it to these two
ahbeng
ahbeng•6d ago
is that /volume1/docker/immich/postgres defined at your host?
secret
secretOP•6d ago
i think this was probably it yeah this is the permanant link
secret
secretOP•6d ago
No description
secret
secretOP•6d ago
used copy path
ahbeng
ahbeng•6d ago
ah.. macs 🙂 love the volume1..
secret
secretOP•6d ago
ill update this thread by the time the next release comes out hahaha yeah its on my nas
ahbeng
ahbeng•6d ago
ok.. remove the "#./postgres" hope that works now
secret
secretOP•6d ago
honestly vscode is goated for docker things yeah gotcha thanks for the help
Zeus
Zeus•6d ago
Well the database shouldn’t be on the NAS
ahbeng
ahbeng•6d ago
that's a good point too. unless you can guarantee that its always mounted correctly
Zeus
Zeus•6d ago
Even if it is, the data integrity guarantees are not the same
Mraedis
Mraedis•6d ago
To be clear, you can have a database in the network what you can't have is the container running on a host with network-mounted storage
secret
secretOP•6d ago
Sorry to clarify everything is on the nas
ahbeng
ahbeng•6d ago
ah... host == nas too then
secret
secretOP•6d ago
yeah
secret
secretOP•6d ago
No description
secret
secretOP•5d ago
reset again Honestly not an immich issue Last time I used it to update jellyfin it reset that too
FlrdB
FlrdB•5d ago
i just updated with dockge without any problems.
secret
secretOP•5d ago
hmm interesting do you mind if i see your dockge compose file here is my dockge one
FlrdB
FlrdB•5d ago
FlrdB
FlrdB•5d ago
Oh sorry this is my immich one.
Mraedis
Mraedis•5d ago
volumes: model-cache: null
what
secret
secretOP•4d ago
see this one this ones the actual file not sure why it shows as that in dockge

Did you find this page helpful?