> Legacy repository migration > All existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be moved from the public catalog (d

> Legacy repository migration > All existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be moved from the public catalog (docker.io/bitnami) to the Bitnami Legacy repository (docker.io/bitnamilegacy). This legacy catalog will receive no further updates or support and should only be used for temporary migration purposes. This sucks, I used to like the Bitnami container images (didn't need the Helm charts) because the images were consistent and consistently nice (documentation, persistent storage, configuration, sizes), but now I need to move off of those. Basically, I'll need to move to the regular upstream images for: * web servers (Apache2 because it's well suited for my needs, but the same would apply to Nginx and Caddy) * relational DBs (MariaDB, though I'm moving over to MySQL 8 for any software that needs it due to their 11 release having compatibility issues with MySQL drivers; as well as PostgreSQL) * key value stores (Redis) * document stores (MongoDB) * message queues (RabbitMQ and NATS) * S3 compatible blob stores (MinIO and SeaweedFS) * utility containers (like Trivy) (either that, or I'll need to build them myself if the Dockerfiles remain available) I'll stay away from Broadcom as much as possible. Edit: > Helm charts and container images' open-source code will continue to be maintained up-to-date and accessible on GitHub under the Apache 2 license. Hmmm: https://github.com/bitnami/containers/tree/main/bitnami/mariadb/11.4 https://github.com/bitnami/containers/tree/main/bitnami/mari... and https://github.com/bitnami/containers/commit/7651d48119a1f3fb106f9a6f83dc430b25052133 https://github.com/bitnami/containers/commit/7651d48119a1f3f...