Errors after upgrading to 1.4.0+v2.5.6 #6
Open
opened 2026-03-02 20:37:46 +00:00 by notplants
·
3 comments
No Branch/Tag Specified
main
renovate/docker.io-valkey-valkey-9
renovate/ghcr.io-immich-app-postgres-16.x
upgrade-1.7.0+v2.7.5
upgrade-2.6.2
backup
feature/immich-postgres
storage
feature/healthcheck
external-storage
1.10.0+v3.1.0
1.9.0+v3.0.1
1.8.0+v2.7.5
1.6.0+v2.7.5
1.5.1+v2.6.3
1.4.0+v2.6.3
1.4.0+v2.5.6
1.3.0+v2.4.1
1.1.0+v2.4.1
1.0.0+v2.2.1
0.3.0+v1.142.0
0.2.1+v1.136.0
0.2.0+v1.142.0
0.1.3+v1.131.3
0.1.2+v1.131.3
0.1.1+release
0.1.0+latest
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
appletalk
arjan
basebuilder
BornDeleuze
Brooke
carla
cas (Cassowary)
codegod100
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
flancian
Frando
hermzz (Hermann Käser)
iexos
jade (Jade Ambrose)
javielico (Javielico)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
marlon (marlon)
mayel
mirsal
moosemower
moritz
nicksellen (Nick Sellen)
notplants
oxaliq (sorrel)
p4u1
pau
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
PhiNatalie
renovate-bot (Comrade Renovate Bot)
ripclap
rix
rscmbbng
sef (sef)
simon
sixsmith (Sixsmith)
stevensting
tobias
trav (Trav Fryer)
val (val (he/him))
vaznasty
virtualboys
wolcen (Chris Thompson)
wykwit
xynosis
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/immich#6
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
after the upgrade, the app container is no longer starting, and I am seeing these errors:
I guess because the db_password was now changed to be a secret?
need to debug this
Commands I used to fix if anyone else runs into this:
then
I just checked: db_secret was inserted in 1.2.0:
811fbf6f68I didn't deploy it before, so thanks for this hint and glad you fixed it.
Perhaps we should edit the release notes of 1.2.0 with your hint?
@val makes sense! and yes if there are not many users of this recipe than adding a release note would be the easiest way (or if we are the only users than maybe dont even need that, or folks would find this issue if they get confused)
in an ideal world, i would add an entrypoint to the container that automatically does that postgres command if its not done already, so that the migration would happen automatically (but probably only helpful if there were more users)