←back to thread

The Deletion of Docker.io/Bitnami

(community.broadcom.com)
329 points zdkaster | 5 comments | | HN request time: 0.78s | source
1. rahkiin ◴[] No.45049100[source]
It is sad to see how Broadcom cannot do padding right for mobile…

But on topic: why not create docker.io/bsi and let /bitnami as is without new updates? Then nothing breaks; it just won’t be possible to do upgrades. You’ll then figure out why and possibly seamlessly switch to your own build or BSI.

replies(3): >>45049311 #>>45050773 #>>45051041 #
2. orthoxerox ◴[] No.45049311[source]
Because "bitnami" has brand value. It makes business sense to reuse the name for the new service you are trying to sell.
replies(1): >>45049550 #
3. Aeolun ◴[] No.45049550[source]
Any brand value that bitnami has will be entirely destroyed by this incomprehensible change. People will associate the ‘bitnami’ namespace with “can’t possible utilize for long term production use”
4. cube00 ◴[] No.45050773[source]
> It is sad to see how Broadcom cannot do padding right for mobile…

It's on brand when you consider how badly the styling in Rally needs an update.

5. david_allison ◴[] No.45051041[source]
> But on topic: why not create docker.io/bsi and let /bitnami as is without new updates?

If people are relying on you for automatic security updates, and you've decided to no longer provide these updates [for free], users should opt in to accept the risk.

This would normally require user action (after a period of warnings/information), and having the fix look 'obviously' unsafe (`/bitnami ` ->`/bitnamilegacy`) feels reasonable.