←back to thread

We Need to Talk About Docker Hub

(www.linuxserver.io)
128 points darthShadow | 1 comments | 24 Jan 25 11:40 UTC | HN request time: 0s | source
Show context
ricardbejarano ◴[24 Jan 25 12:15 UTC] No.42812378[source]▶
Run your own registry.
replies(3): >>42812402 #>>42812415 #>>42812602 #
TZubiri ◴[24 Jan 25 12:20 UTC] No.42812415[source]▶
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 level abstraction.

If you want to replace burgers, just buy a slab of meat and put it in the fire or bake your own bread. You don't need to make preservants and buy artificial sweeteners, etc...

replies(7): >>42812470 #>>42812473 #>>42812476 #>>42812525 #>>42812526 #>>42812553 #>>42812606 #
thomasfedb ◴[24 Jan 25 12:30 UTC] No.42812476{3}[source]▶
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.

replies(1): >>42812556 #
1. TZubiri ◴[24 Jan 25 12:42 UTC] No.42812556{4}[source]▶
One of the core arguments is that DockerHub is the default for Docker. The article shows that the URL for dockerhub is baked into Docker and is used when no registry is specified.