Replacing deprecated Bitnami images

In August 2025 Bitnami moved its free versioned container images tobitnamilegacy, which receives no further updates or security fixes, and put maintained images behind Bitnami Secure Images. If you are still pulling from docker.io/bitnami, you are running software that stopped being patched.

Bitnami builds 379 images. Minimal has an equivalent for64 of them, free, with no account and no paid tier — which leaves307 with no replacement here. Both lists are below, generated from Bitnami's own repository rather than compiled by hand, and ordered by Docker Hub pull count so the ones people actually run come first.

Direct replacements

Same upstream software. Configuration and paths follow the upstream project's conventions rather than Bitnami's, so read the migration notes below before swapping.

What Minimal does not cover

307 of Bitnami's 379 images have no Minimal equivalent. The most-pulled of them:

Two of these are deliberate rather than pending: mongodb (SSPL) andelasticsearch (Elastic License) are not open source, so they will not be added.opensearch is the closest available substitute for Elasticsearch. The rest are simply not built yet.

The three things that will break

A Bitnami image is not shaped like a Minimal one, so this is not a pure reference swap. Expect these:

Bitnami's /opt/bitnami paths do not exist

Bitnami standardises config, data and binaries under /opt/bitnami/<app>. Minimal follows each project's own upstream layout instead. Any volume mount, config path orcommand referencing /opt/bitnami needs rewriting. Each image's Specifications tab lists its actual entrypoint and paths.

No shell, so Bitnami's entrypoint scripts do not port

Bitnami images ship a shell and a substantial libentrypoint.sh layer that renders config from environment variables. Minimal production images have no shell at all, so that pattern cannot be carried across — configure the software directly, or render config in an init container.

Different non-root UID

Bitnami images conventionally run as UID 1001. Minimal uses65532. Existing volumes written by a Bitnami container will be owned by the wrong UID, so set fsGroup or chown the data before cutting over.On a database volume, test this on a copy first.

A note on Helm charts

Most Bitnami usage is via Bitnami Helm charts, and those charts assume the Bitnami image layout throughout — the paths, the entrypoint scripts and the UID above. Overridingimage.repository to point at a Minimal image will generally not work on its own. Migrating the chart is a larger job than migrating the image, and this page does not pretend otherwise.

Try one

docker pull ghcr.io/rtvkiz/minimal-postgres-slim:latest
grype ghcr.io/rtvkiz/minimal-postgres-slim:latest

The general migration steps — tags, verification, rollout order — are inthe migration guide, and apply whichever base you are coming from. Full catalog: 150 images.

This page is generated, not written. The image list comes frombitnami/containers(one directory per image Bitnami builds); pull counts and pullability come from the Docker Hub API. A row appears only when both sources agree — 8 images Bitnami builds have no pullable Docker Hub repository and are excluded. Generated2026-10-26. Bitnami's catalog changes are documented by Broadcom inbitnami/containers #83267. Details there change; that issue, not this page, is the authority on what Bitnami currently publishes. Statements about Minimal are checkable from the verify page.