Hi,
I noticed that the Yatai quick-start scripts (scripts/quick-install-yatai.sh), build scripts (scripts/build-images.sh), and the official documentation (docs/source/installation/yatai.rst) rely directly on the bitnami/postgresql-repmgr Docker image.
The Problem
Bitnami has recently restricted public access to their Docker images, placing them behind a paywall with strict rate limits. Relying on docker.io/bitnami/postgresql-repmgr directly in your kubectl run or quick-install-yatai.sh commands now frequently results in pull access denied errors.
This severely impacts the initial developer experience, as users following the "Quick Tour" or official documentation will likely fail to spin up the local Yatai deployment.
Proposed Solution
I suggest switching the hardcoded image references to soldevelo/postgresql-repmgr.
This image is a free, actively maintained, and fully open-source fork of the original Bitnami image.
Crucially, it is a drop-in replacement:
- It accepts the exact same environment variables (like
PGPASSWORD=$PG_PASSWORD).
- It maintains the same internal paths and
repmgr setup.
- Your existing installation scripts and documentation commands will work immediately without requiring any structural changes.
(Note: SolDevelo maintains a growing library of open-source, Bitnami-compatible images to help the community bypass these new restrictions. You can find the source code and other images here: https://github.com/SolDevelo/containers)
Suggested Changes:
In scripts/quick-install-yatai.sh and docs/source/installation/yatai.rst:
# Old
--image docker.io/bitnami/postgresql-repmgr:14.4.0-debian-11-r13
# New
--image docker.io/soldevelo/postgresql-repmgr:14.4.0-debian-11-r13
In scripts/build-images.sh:
# Old
bitnami/postgresql-repmgr:11.14.0-debian-10-r12
# New
soldevelo/postgresql-repmgr:11.14.0-debian-10-r12
I can submit a Pull Request to update the image references across the scripts and docs to ensure new users can evaluate Yatai without friction. Would you be open to that?
Hi,
I noticed that the Yatai quick-start scripts (
scripts/quick-install-yatai.sh), build scripts (scripts/build-images.sh), and the official documentation (docs/source/installation/yatai.rst) rely directly on thebitnami/postgresql-repmgrDocker image.The Problem
Bitnami has recently restricted public access to their Docker images, placing them behind a paywall with strict rate limits. Relying on
docker.io/bitnami/postgresql-repmgrdirectly in yourkubectl runorquick-install-yatai.shcommands now frequently results inpull access deniederrors.This severely impacts the initial developer experience, as users following the "Quick Tour" or official documentation will likely fail to spin up the local Yatai deployment.
Proposed Solution
I suggest switching the hardcoded image references to
soldevelo/postgresql-repmgr.This image is a free, actively maintained, and fully open-source fork of the original Bitnami image.
Crucially, it is a drop-in replacement:
PGPASSWORD=$PG_PASSWORD).repmgrsetup.(Note: SolDevelo maintains a growing library of open-source, Bitnami-compatible images to help the community bypass these new restrictions. You can find the source code and other images here: https://github.com/SolDevelo/containers)
Suggested Changes:
In
scripts/quick-install-yatai.shanddocs/source/installation/yatai.rst:In
scripts/build-images.sh:I can submit a Pull Request to update the image references across the scripts and docs to ensure new users can evaluate Yatai without friction. Would you be open to that?