←back to thread

The Deletion of Docker.io/Bitnami

(community.broadcom.com)
329 points zdkaster | 4 comments | 28 Aug 25 04:37 UTC | HN request time: 0s | source
Show context
notimetorelax ◴[28 Aug 25 05:07 UTC] No.45048589[source]▶
Is anyone working on mirroring the images and keeping them updated?
replies(3): >>45048778 #>>45048951 #>>45049063 #
mrweasel ◴[28 Aug 25 06:25 UTC] No.45049063[source]▶
Updating the Bitnami images is probably a bit of a challenge. From looking at them last year, I believe that they are build around a Bitnami style/framework. They are confusing at best.

If you're Bitnami it probably made sense to do it the image the way they did, but for everyone else, it's just a massive complication.

Personally I don't understand why anyone would have opted to use the Bitnami images for most things. They are really large and complex images and in most cases you'd probably be better of building your own images instead.

My guess is that there's a very small overlap between people who want to maintain Docker images, and the people who chose to run Bitnamis images.

replies(2): >>45049242 #>>45049305 #
1. tux3 ◴[28 Aug 25 06:56 UTC] No.45049242[source]▶
The Docker images are complex for the sake of the Helm charts, which sometimes need to pass down tons of parameters

These aren't just for your laptop, they're supposed to be able to run in prod

I'm still stuck with 3 bitnami charts that I keep updated by building from source, which includes also building the images, all on our private registry.

replies(1): >>45049387 #
2. mrweasel ◴[28 Aug 25 07:18 UTC] No.45049387[source]▶
That makes some sense. I've only used Bitnami images with Docker compose or as standalone containers. In those case you're frequently better of just mounting in a configuration file, but that won't really work in Kubernetes.

I would argue that if you run Kubernetes, then you frequently already have the resource to maintain your own images.

replies(2): >>45050852 #>>45050960 #
3. raziel2p ◴[28 Aug 25 11:27 UTC] No.45050852[source]▶
You'd also have to maintain the helm chart, which is arguably far more work.

If you don't need the bitnami helm chart functionality, using more stock container images is easy and preferable.

4. wink ◴[28 Aug 25 11:42 UTC] No.45050960[source]▶
I had not used bitnami images for.. probably 5 years at this point and they always seemed servicable in a pinch, usually used for testing and I when I brought this up recently I was also told (by k8s users) that the helm stuff is probably what actually has most people up in arms because it is very common. We're the minority who remember bitnami as a non-critical choice among many.