Can't pull image for mongodb 5.0.6 about bitnami-compat HOT 10 CLOSED

the earliest compat tag I can find is 5.0.10 https://hub.docker.com/r/zcube/bitnami-compat-mongodb/tags?page=1&ordering=-last_updated&name=5.0.

from bitnami-compat.

@ddelange Hi our team used this.
https://github.com/zcube/bitnami-compat/pkgs/container/bitnami-compat%2Fmongodb/23142914?tag=5.0.6

from bitnami-compat.

it was working until recently

from bitnami-compat.

I cleaned up old images from ghcr. It seems like an erased image at that time.

from bitnami-compat.

The issue is that this repository is a free repository to keep too many and large images.

from bitnami-compat.

You can build 5.0.6 by modifying the version of containers/bitnami/mongodb/5.0/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json.

git clone --recursive https://github.com/ZCube/bitnami-compat
cd bitnami-compat
...
# fix containers/bitnami/mongodb/5.0/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
# rm -rf containers/bitnami/mongodb/6.0
...
go run main.go generate --app=mongodb
go run main.go build --app=mongodb --tag {{your-docker-registry}}/bitnami-compat/ --push --platforms=linux/amd64,linux/arm64 

from bitnami-compat.

@ZCube do you have to make space manually? will CI error otherwise? I think untagged images might be garbage collected at some point

from bitnami-compat.

@ddelange https://github.com/ZCube/bitnami-compat/blob/main/.github/workflows/clean-old-images.yml
I had done that work through this workflow. Perhaps because of the cache used to build the image, the tagged image was also corrupted and could not be used.

from bitnami-compat.

@ETtestim I will not recover the 5.0.6 image because 5.0.14 is compatible with 5.0.6. Please let me know if you really need it.

from bitnami-compat.

Hi @ZCube thanks for your quick reply.
We will use 5.0.14.

from bitnami-compat.