←back to thread

The Deletion of Docker.io/Bitnami

(community.broadcom.com)
333 points zdkaster | 1 comments | 28 Aug 25 04:37 UTC | HN request time: 0.203s | source
Show context
morellonet ◴[28 Aug 25 12:56 UTC] No.45051606[source]▶
If you’re looking for an alternative here, we (the team that built Twistlock) launched Minimus a few months ago to provide near zero CVE images built continuously from source. We have long experience in this space (we even wrote NIST SP 800-190) and I’d love to talk if we could help anyone. We also have drop in replacement images and charts for Bitnami, as we describe here: https://www.minimus.io/post/the-bitnami-pricing-changes-what...

If anyone has tech questions about how it all works, tools we use, customer scenarios, etc I’d be happy to discuss.

replies(4): >>45052737 #>>45053063 #>>45053091 #>>45054839 #
1. carrodher ◴[28 Aug 25 17:36 UTC] No.45054839[source]▶
Let me rewrite the comparison used in the "Example: Using Bitnami vs. Minimus" section of the blog post:

Using Bitnami Secure Images: You pull a versioned PostgreSQL image built on a minimal-attack-surface OS (Photon). When a CVE is disclosed or a new upstream version is released, Bitnami’s automation takes care of everything: a new container image (and Helm chart, if applicable) is built, tested, and published to your registry within hours. All you need to do is update to the latest version; no manual CVE monitoring, triage, or patching required.