Bitnami images such as bitnami/kafka stopped pulling from Docker Hub
Fix it fast
Most common cause, 1 of 3The tag was moved out of docker.io/bitnami
Change the namespace to bitnamilegacy to unblock deploys.
# docker-compose.yml
services:
kafka:
image: docker.io/bitnamilegacy/kafka:3.9Short answer
Bitnami removed most images and all versioned tags from docker.io/bitnami in 2025. Old tags were moved to docker.io/bitnamilegacy, which gets no updates, and only a small set of hardened images remains free, on the latest tag. A pull of bitnami/kafka:3.9 therefore finds no manifest. Point the image at bitnamilegacy to get running, then move to a maintained image.
Which cause do you have?
Ask the registry directly whether the tag exists in each Bitnami namespace. This works without Docker installed.
for r in bitnami/kafka bitnamilegacy/kafka; do
tok=$(curl -s "https://auth.docker.io/token?service=registry.docker.io&scope=repository:$r:pull" | python3 -c "import sys,json;print(json.load(sys.stdin)['token'])")
printf "%s:3.9 -> " "$r"
curl -s -o /dev/null -w "%{http_code}\n" -H "Authorization: Bearer $tok" \
-H "Accept: application/vnd.oci.image.index.v1+json, application/vnd.docker.distribution.manifest.list.v2+json" \
"https://registry-1.docker.io/v2/$r/manifests/3.9"
doneThen find the line you see in this list and open its fix:
- 1The tag was moved out of docker.io/bitnami
The registry answers 404 MANIFEST_UNKNOWN for bitnami/<app> and 200 for bitnamilegacy/<app> with the same tag - 2A Bitnami Helm chart still references docker.io/bitnami
Pods stay in ImagePullBackOff and kubectl describe shows a docker.io/bitnami image - 3You need an image that still gets updates
The legacy image works, but you cannot run unpatched software in production
What does the error look like?
manifest unknown: manifest unknown{"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":"unknown tag=3.9"}]}Pods stuck in ImagePullBackOff on a docker.io/bitnami image
Cause 1 of 3
The tag was moved out of docker.io/bitnami
You seeThe registry answers 404 MANIFEST_UNKNOWN for bitnami/<app> and 200 for bitnamilegacy/<app> with the same tag
Check
Bitnami's catalog announcement says all existing images, including versioned tags, moved from docker.io/bitnami to docker.io/bitnamilegacy, and that the legacy catalog gets no further updates. On 20 November 2026 the registry returned 404 for bitnami/kafka tags 3.9, 3.9.0 and latest, and 200 for the same tags under bitnamilegacy/kafka.
grep -rnE "image: *(docker.io/)?bitnami/" docker-compose*.yml compose*.yaml k8s 2>/dev/nullFix
Change the namespace to bitnamilegacy to unblock deploys. Treat it as temporary: the images will not receive security fixes.
# docker-compose.yml
services:
kafka:
image: docker.io/bitnamilegacy/kafka:3.9Verify
The image pulls and the container starts.
docker compose pull kafka && docker compose up -d kafkaConfirmed by github.com
Cause 2 of 3
A Bitnami Helm chart still references docker.io/bitnami
You seePods stay in ImagePullBackOff and kubectl describe shows a docker.io/bitnami image
Check
The chart's default values point every container at the old repository. The same announcement offers a temporary workaround: keep the chart version and override the repository parameter of each image to the legacy namespace.
kubectl get pods -A -o jsonpath='{..image}' | tr ' ' '\n' | grep bitnami/ | sort -uFix
Override image.repository (and any sidecar or metrics image) in your values file, then upgrade the release with the same chart version.
# values.yaml
image:
repository: bitnamilegacy/kafka
helm upgrade my-kafka <chart> -f values.yaml --version <same-version>Verify
All pods reach Running and describe shows the bitnamilegacy image.
kubectl get pods -l app.kubernetes.io/instance=my-kafkaConfirmed by github.com
Cause 3 of 3
You need an image that still gets updates
You seeThe legacy image works, but you cannot run unpatched software in production
Check
The free community tier keeps only a limited set of hardened images at hub.docker.com/u/bitnamisecure, and only their latest tag. Many apps are not in that set; there was no bitnamisecure/kafka repository on 20 November 2026.
curl -s 'https://hub.docker.com/v2/repositories/bitnamisecure/?page_size=100' | python3 -c "import sys,json;print([r['name'] for r in json.load(sys.stdin)['results']])"Fix
Use the bitnamisecure image if your app is listed and the latest tag is acceptable; otherwise move to the project's own official image (for example apache/kafka or postgres) and adapt the environment variables, which differ from Bitnami's.
services:
kafka:
image: apache/kafka:4.1.0
# Bitnami's KAFKA_CFG_* variables do not apply here; use the image's own documented settingsVerify
The service starts with its data volume and clients connect.
docker compose up -d && docker compose logs -f kafkaConfirmed by raw.githubusercontent.com
How do I stop it coming back?
- Mirror third-party images you depend on into your own registry.
- Pin images by digest in production so a vanished tag fails loudly in CI, not during a scale-up.
- Watch the upstream repository of each base image for catalog announcements.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies: