From 8313b5d998b97eb889f166613edf7dc7b1b64af9 Mon Sep 17 00:00:00 2001 From: Giteabot Date: Wed, 3 Sep 2025 23:15:50 +0800 Subject: [PATCH] Switch `bitnami` images to `bitnamilegacy` on CI (#35402) (#35403) Backport #35402 by @silverwind As per https://github.com/bitnami/containers/issues/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 --- .github/workflows/pull-db-tests.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/pull-db-tests.yml b/.github/workflows/pull-db-tests.yml index 55c2d2bf5e..faf6a90e1b 100644 --- a/.github/workflows/pull-db-tests.yml +++ b/.github/workflows/pull-db-tests.yml @@ -31,7 +31,7 @@ jobs: minio: # as github actions doesn't support "entrypoint", we need to use a non-official image # that has a custom entrypoint set to "minio server /data" - image: bitnami/minio:2023.8.31 + image: bitnamilegacy/minio:2023.8.31 env: MINIO_ROOT_USER: 123456 MINIO_ROOT_PASSWORD: 12345678 @@ -113,7 +113,7 @@ jobs: ports: - 6379:6379 minio: - image: bitnami/minio:2021.3.17 + image: bitnamilegacy/minio:2021.3.17 env: MINIO_ACCESS_KEY: 123456 MINIO_SECRET_KEY: 12345678 @@ -155,7 +155,7 @@ jobs: services: mysql: # the bitnami mysql image has more options than the official one, it's easier to customize - image: bitnami/mysql:8.0 + image: bitnamilegacy/mysql:8.0 env: ALLOW_EMPTY_PASSWORD: true MYSQL_DATABASE: testgitea