fix: discover DB containers by their configured image, not the docker ps name #2
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
Priority: High
Priority: Low
Priority: Medium
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Scripts/dbs-backup!2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/discover-by-configured-image"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happened
From 15.10. on, the nightly backup found no Postgres databases ("No Postgres DB containers discovered"). supabase-db, supabase-stage-db and both billing DBs went two nights without a backup; Kill Bill was not affected. Monitoring raised "Backup KRITISCH veraltet" on 17.10.
Cause: the Postgres image also carried a second name (public.ecr.aws/supabase/postgres, pulled by the CI migration check). A docker image prune in the app deploy on 15.10. then removed the name supabase/postgres. The containers kept running, but docker ps showed only the image ID, so the name-based discovery matched nothing.
Already done on bnet006 (17.10.)
Change
Checked on bnet006: discovers supabase-db, supabase-stage-db, both billing DBs and both Kill Bill DBs.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.