Bitnami image pull errors

Overview

Bitnami has discontinued publishing image tags for several of the Helm chart dependencies FOSSA historically relied on. When a tag your chart references is no longer available, the affected pods fail to start with ErrImagePull or ImagePullBackOff.

FOSSA maintains mirrored copies of these images so you can keep running. Use the fixes below as a short-term bridge; the long-term solution is to upgrade to a fossa-core version that pulls images from FOSSA's quay.io/fossa registry.

ErrImagePull / ImagePullBackOff on bitnami/postgresql, bitnami/postgresql-exporter, or bitnami/os-shell

Cause: Bitnami stopped publishing the Postgres image tags referenced by the chart's database dependencies.

Fix: Point the existing Bitnami Postgres chart at FOSSA's mirrored images on quay.io. Run the matching command for each database you deploy:

# Core databasehelm upgrade -i fossa-core-db oci://registry-1.docker.io/bitnamicharts/postgresql --set global.security.allowInsecureImages=true --set global.imageRegistry=quay.io --set image.repository=fossa/postgres --set volumePermissions.image.repository=fossa/os-shell --set metrics.image.repository=fossa/postgres-exporter --version 16.4.7 -n fossa --reuse-values # Sparkle databasehelm upgrade -i fossa-sparkle-db oci://registry-1.docker.io/bitnamicharts/postgresql --set global.security.allowInsecureImages=true --set global.imageRegistry=quay.io --set image.repository=fossa/postgres --set volumePermissions.image.repository=fossa/os-shell --set metrics.image.repository=fossa/postgres-exporter --version 16.4.7 -n fossa --reuse-values # Hubble databasehelm upgrade -i fossa-hubble-db oci://registry-1.docker.io/bitnamicharts/postgresql --set global.security.allowInsecureImages=true --set global.imageRegistry=quay.io --set image.repository=fossa/postgres --set volumePermissions.image.repository=fossa/os-shell --set metrics.image.repository=fossa/postgres-exporter --version 16.4.7 -n fossa --reuse-values

ErrImagePull / ImagePullBackOff on bitnami/redis, bitnami/redis-exporter, bitnami/os-shell, or bitnami/minio

Cause: Bitnami stopped publishing the Redis and MinIO image tags referenced by the chart.

Fix: Point Redis and MinIO at the bitnamilegacy images. Ideally make these changes in your values file:

• Core MinIO: storage.image.repository: bitnamilegacy/minio, storage.image.tag: 2020.6.3, storage.image.registry: docker.io
• Core Redis: redis.image.repository: bitnamilegacy/redis, redis.image.tag: 6.2.9, redis.image.registry: docker.io
• Hubble MinIO: hubble.storage.image.repository: bitnamilegacy/minio, hubble.storage.image.tag: 2020.6.3, hubble.storage.image.registry: docker.io

In a pinch, you can apply the same overrides directly on the command line:

helm upgrade -i fossa fossa/fossa-core --reuse-values --set storage.image.repository=bitnamilegacy/minio --set storage.image.tag=2020.6.3 --set storage.image.registry=docker.io --set redis.image.repository=bitnamilegacy/redis --set redis.image.tag=6.2.9 --set redis.image.registry=docker.io --set hubble.storage.image.repository=bitnamilegacy/minio --set hubble.storage.image.tag=2020.6.3 --set hubble.storage.image.registry=docker.io --version=3.0.3

Long-term solution

These mirrored-image workarounds keep an existing chart running, but they're not a permanent fix. We strongly recommend upgrading to fossa-core 4.4.1+, which pulls images from FOSSA's quay.io/fossa registry rather than depending on Bitnami tags. See Upgrading FOSSA.

Still stuck?

If pods continue to fail to pull images after applying these changes, collect a debug bundle and share it with FOSSA support.