Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We Need to Talk About Docker Hub

linuxserver.io

Post reply on HN
Print view View original

11–20 of 153 posts

Re: We Need to Talk About Docker Hub

#11

Post by sealeck »

concerndc1tizen wrote: post #6

If you don't like it, then why don't you use a different provider? If you want free stuff, is your strategy to smear them into giving you more free stuff? Storage, compute, and traffic, isn't free. You've been the beneficiary of charity for years. Yes, the open source community has relied on this implicit charity as a parasite, by exploiting whatever free services they could. And now we're paying the price, as you sa…

This is really a question of framing. The other way you can look at it is: Docker has benefitted from a community adopting its products, and developing software that makes Docker more useful. As someone who sells Docker services, you benefit from a greater market size.

It's like how WordPress have benefitted from people authoring plugins – even though wordpress.org has hosted them for "free", this has been good commercial sense as it allows them to sell more WordPress.com to people.

Re: We Need to Talk About Docker Hub

#12

Post by regularfry »

hobofan wrote: post #5
TZubiri wrote: post #3

[flagged]

> It's a naturally vendor neutral tech so migrating should be trivial. So are the OCI standards that grew out of Docker and now are mostly used separate from (official) Docker. Is there even a vendor neutral VM image format?

Yeah, raw disk images. If you give me a block device, I can boot off it.

Slightly less trivially, anything qemu-img handles should probably be considered at least in the neutral direction, if not actually neutral.

Re: We Need to Talk About Docker Hub

#14

Post by TZubiri »

hobofan wrote: post #5
TZubiri wrote: post #3

[flagged]

> It's a naturally vendor neutral tech so migrating should be trivial. So are the OCI standards that grew out of Docker and now are mostly used separate from (official) Docker. Is there even a vendor neutral VM image format?

>Is there even a vendor neutral VM image format?

The vendor neutral standard is the Operating System. You don't need the format of the OS at disk to be standardized, that assumes a wild misconception of OS.

The OS integrates with hardware so you typically can't just copy an image between different machines and expect it to work, what's standard is the installation procedure which can be part OS provided and part hardware manufacturer/host provided.

Yes the process for installing the operating and configuring system is a bit of glue that might not be vendor neutral, but if you are obsessing over that and spending time with stuff like terraform you are missing the forest for the trees. It's like open source zealots complaining that github is closed source. You are 99% of the way there, forget about the 1% last mile and just port it manually.

Re: We Need to Talk About Docker Hub

#15

Post by thomasfedb »

concerndc1tizen wrote: post #6

If you don't like it, then why don't you use a different provider? If you want free stuff, is your strategy to smear them into giving you more free stuff? Storage, compute, and traffic, isn't free. You've been the beneficiary of charity for years. Yes, the open source community has relied on this implicit charity as a parasite, by exploiting whatever free services they could. And now we're paying the price, as you sa…

Well, by their own amount of events they have and are - they’ve changed their default registry.

If Docker advertises an open source program, it’s completely fair to be critical if they’re not delivering as advertised.

Re: We Need to Talk About Docker Hub

#16

Post by bananapub »

TZubiri wrote: post #7
ricardbejarano wrote: post #2

Run your own registry.

Or run no registry. Here's a port from a Dockerfile to just a vm: FROM Debian CMD apt-get install thing CMD curl blabla/install.sh Pretty much converts to: aws-cli ec2 launch-instance ssh user@server apt-get install thing ssh user@server curl blabla/install.sh In general, everytime you dispense of a high level abstraction, the solution is not to replicate the high level abstraction, but to build directly at a lower l…

what a profoundly useless comment. "why don't you do something else, unrelated, which doesn't solve any of the problems you have?" is absolutely the Ur-HN Reply.

Re: We Need to Talk About Docker Hub

#17

Post by bartread »

TZubiri wrote: post #7
ricardbejarano wrote: post #2

Run your own registry.

Or run no registry. Here's a port from a Dockerfile to just a vm: FROM Debian CMD apt-get install thing CMD curl blabla/install.sh Pretty much converts to: aws-cli ec2 launch-instance ssh user@server apt-get install thing ssh user@server curl blabla/install.sh In general, everytime you dispense of a high level abstraction, the solution is not to replicate the high level abstraction, but to build directly at a lower l…

Careful now: people will start accusing you of NIH.

But I fully agree with you. Likely what you need is a tiny subset of the capabilities wrapped up by the higher level abstraction, so implement them directly.

Over time you may find you need additional capabilities (although that's far from a given) and, if and when you do, you'll need to make decisions about whether to implement them directly, or wrap everything in a higher level abstraction (or use a third party abstraction).

The point is that if you ever do need these additional capabilities there's a good chance it's because you've been successful enough to enter "good problem to have" territory because you didn't waste time getting distracted by them earlier on and instead chose to focus on work that enabled that success.

Re: We Need to Talk About Docker Hub

#18

Post by thomasfedb »

TZubiri wrote: post #7
ricardbejarano wrote: post #2

Run your own registry.

Or run no registry. Here's a port from a Dockerfile to just a vm: FROM Debian CMD apt-get install thing CMD curl blabla/install.sh Pretty much converts to: aws-cli ec2 launch-instance ssh user@server apt-get install thing ssh user@server curl blabla/install.sh In general, everytime you dispense of a high level abstraction, the solution is not to replicate the high level abstraction, but to build directly at a lower l…

The article is about DockerHub, not Docker.

Containers aren’t the only solution to every problem but they’re a decent hammer for a lot of nails.

Re: We Need to Talk About Docker Hub

#20

Post by whois »

concerndc1tizen wrote: post #6

If you don't like it, then why don't you use a different provider? If you want free stuff, is your strategy to smear them into giving you more free stuff? Storage, compute, and traffic, isn't free. You've been the beneficiary of charity for years. Yes, the open source community has relied on this implicit charity as a parasite, by exploiting whatever free services they could. And now we're paying the price, as you sa…

Your response feels in bad faith. Docker is the default registery. That gives them n amount of responsibility. Not to mention organizations should be accountable for their bad behavior. Don't give them a pass.
Post reply on HN