←back to thread

The Deletion of Docker.io/Bitnami

(community.broadcom.com)
329 points zdkaster | 1 comments | | HN request time: 0s | source
Show context
greatgib ◴[] No.45049298[source]
I don't want to discount the work they are doing, and that it has no value, but a little bit shocking that they expect to go all commercial with this, in the Oracle way, while just "packaging" and so relying on open source software that they will not contribute to.

Also, I'm a little bit wondering at how much all of this is really copyrightable in the end. Because if you keep it private I understand, but here it is basically for each package just a few lines, recipes to build the components that they don't own. Like trying to copyright the line "make build".

And it might be each the single and obvious way to package the thing anyway.

And speaking at the built artefacts, usually a binary distribution of third party open source software with common license should preserve the same rights to the user to access the source code, the instructions to build, and the right to redistribute...

replies(2): >>45049473 #>>45049478 #
nopurpose ◴[] No.45049473[source]
"Makefile" they have written and copyrighting is very non trivial and there are many man-months of effort. Configuring all sorts of software just with env vars and make it usable is not an easy feat.

Have a look at https://github.com/bitnami/containers/tree/main/bitnami/post... as example.

It might be worth a commercial license for some of their current user-base, no doubt.

replies(3): >>45049694 #>>45056383 #>>45056489 #
tomalbrc ◴[] No.45049694[source]
This has to be a joke, right? Months of effort for a makefile? In which world do people live these days
replies(6): >>45049733 #>>45049977 #>>45049987 #>>45051104 #>>45051310 #>>45056458 #
draw_down ◴[] No.45049977{3}[source]
It would only take you a weekend!
replies(1): >>45050499 #
jeltz ◴[] No.45050499{4}[source]
It is a lot of work but it is work that for the most part should not have been done. I took a quick look at the code (since I know PG very well) and I would not recommend anyone to use that mess off Bash code which configures PostgreSQL in an annoying and incorrect way and exposed some arbitrarily select settings in the environment (some very rarely used) while you have to do most in the config file. Better to just write your own Docker image for scratch, or use the official PG image of your needs are simple.

This is what happens if you merge every feature request you get and do not have a clear plan or architecture. After reading the code I am happy they are deleting the images, at least if this one is typical.

As a PostgreSQL expert I can write a much better image which suits my needs in one day, which I have also done several times. It would be harder for a non-expery but I do not think a non-expert should use this image due to some footguns I spotted. This kind of generic image is a bad idea and very hard to build.

replies(2): >>45050792 #>>45051898 #
1. bethekidyouwant ◴[] No.45051898{5}[source]
Hindsight is 2020, there’s now helm/kubernetes operator under the cloud native umbrella. I’m sure they took in all the mistakes from here. This helm chart is getting long in the tooth, but is still monumental. Imo running psql on kube is a mistake to begin with but here we are.