Switch bitnami images to bitnamilegacy on CI
#35402
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As per bitnami/containers#83267, my understanding is that the `docker.io/bitnami` images will eventually be deleted or could be affected by future brownouts. To prevent this failure mode, use the images on the `bitnamilegacy` org instead. Long-term, we should replace these images with official ones.
GiteaBot
added
the
lgtm/need 2
silverwind
added
the
skip-changelog
hiifong
approved these changes
Sep 3, 2025
GiteaBot
added
lgtm/need 1
techknowlogick
approved these changes
Sep 3, 2025
GiteaBot
added
lgtm/done
techknowlogick
added
the
backport/v1.24
techknowlogick
added
the
reviewed/wait-merge
GiteaBot
removed
the
reviewed/wait-merge
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this pull request
Sep 3, 2025
As per bitnami/containers#83267, my understanding is that the `docker.io/bitnami` images will be deleted on September 29. To prevent this failure mode, use the images on the `bitnamilegacy` org instead which are snapshots from when they stopped updating them. Long-term, we should replace these images with official ones.
silverwind
added a commit
that referenced
this pull request
Sep 3, 2025
Backport #35402 by @silverwind As per bitnami/containers#83267, my understanding is that the `docker.io/bitnami` images will be deleted on September 29. To prevent this failure mode, use the images on the `bitnamilegacy` org instead which are snapshots from when they stopped updating them. Long-term, we should replace these images with official ones. Co-authored-by: silverwind <me@silverwind.io>
zjjhot
added a commit
to zjjhot/gitea
that referenced
this pull request
Sep 4, 2025
* giteaofficial/main: Switch to pnpm (go-gitea#35274) Switch `bitnami` images to `bitnamilegacy` on CI (go-gitea#35402) Upgrade dependencies (go-gitea#35384) [skip ci] Updated translations via Crowdin # Conflicts: # package-lock.json
techknowlogick
pushed a commit
that referenced
this pull request
Sep 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per bitnami/containers#83267, my understanding is that the
docker.io/bitnamiimages will be deleted on September 29.To prevent this failure mode, use the images on the
bitnamilegacyorg instead which are snapshots from when they stopped updating them. Long-term, we should replace these images with official ones.