fix(image): re-pin bitnami->bitnamilegacy/discourse:3.3.1 (Docker Hub emptied bitnami/discourse) #1

Open
autonomic-bot wants to merge 3 commits from ci/bitnamilegacy-repin into main

bitnami/discourse:3.3.1 is unservable (Docker Hub emptied the namespace; manifest 404). bitnamilegacy/discourse:3.3.1 is the byte-identical archived drop-in (manifest 200, confirmed first-hand). Re-pins both app + sidekiq services. Found via cc-ci enrollment.

bitnami/discourse:3.3.1 is unservable (Docker Hub emptied the namespace; manifest 404). bitnamilegacy/discourse:3.3.1 is the byte-identical archived drop-in (manifest 200, confirmed first-hand). Re-pins both app + sidekiq services. Found via cc-ci enrollment.
autonomic-bot added 1 commit 2026-05-30 09:52:37 +00:00
Docker Hub emptied the bitnami/discourse namespace (manifest 3.3.1 -> 404, tags:[]); Bitnami moved
archived images to the bitnamilegacy namespace. bitnamilegacy/discourse:3.3.1 is the byte-identical
drop-in (manifest -> 200, same /bitnami/discourse paths + /opt/bitnami scripts). Re-pin both app +
sidekiq services; bump 0.7.0 -> 0.8.0. Found via cc-ci enrollment.
autonomic-bot added 1 commit 2026-05-30 14:03:47 +00:00
The db service dumped the DB on backup (pg_dump pre-hook) but shipped no
restore hook, and a file-level restore does not reload into the running
postgres, so a restored backup silently kept the live (un-restored) state.
Add pg_backup.sh (backup=pg_dump|gzip into the postgresql_data volume;
restore=terminate conns + DROP DATABASE WITH FORCE + createdb + reimport),
mount it via a config, and wire the backupbot backup/restore hooks. Same
fix as the immich / mattermost-lts / ghost recipes.
autonomic-bot force-pushed ci/bitnamilegacy-repin from 2fd5e37f55 to 04bb9db7b6 2026-05-30 14:07:00 +00:00 Compare
autonomic-bot force-pushed ci/bitnamilegacy-repin from 04bb9db7b6 to 0926a42d2e 2026-05-30 14:13:11 +00:00 Compare
autonomic-bot force-pushed ci/bitnamilegacy-repin from 0926a42d2e to c8ba2e4e2b 2026-05-30 14:45:23 +00:00 Compare
autonomic-bot force-pushed ci/bitnamilegacy-repin from c8ba2e4e2b to 70891e2fb5 2026-05-30 15:09:09 +00:00 Compare
autonomic-bot force-pushed ci/bitnamilegacy-repin from 70891e2fb5 to 7a2e0e044c 2026-05-30 15:19:28 +00:00 Compare
autonomic-bot added 1 commit 2026-05-30 23:37:33 +00:00
Author
Owner

@notplants — flagging this open PR from the cc-ci build for your review. Per the updated mirror workflow we no longer auto-close superseded/unrelated PRs, so it's left open for you to merge or close at your discretion.

@notplants — flagging this open PR from the cc-ci build for your review. Per the updated mirror workflow we no longer auto-close superseded/unrelated PRs, so it's left open for you to merge or close at your discretion.
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin ci/bitnamilegacy-repin:ci/bitnamilegacy-repin
git checkout ci/bitnamilegacy-repin
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: recipe-maintainers/discourse#1
No description provided.