3 ms·
Back when Docker got popular, maybe 10 years ago, I was behind a slow ADSL connection (less < 2Mbps) and I couldn't stand anything up with it to save my life.
by PaulHoule 2y ago
Back when Docker got popular, maybe 10 years ago, I was behind a slow ADSL connection (less < 2Mbps) and I couldn't stand anything up with it to save my life. Downloads from Docker Hub just wouldn't complete.
I figured some kind of smart download manager and caching system would save the day but frankly I saw Docker as a step backward because I had been doing a really good job of installing 100+ web services on a single server since 2003 or so. [1] [2]
Looking back it, I'm sure that a short timeout was a deliberate decision by the people running Docker Hub, as people with slow internet connections because telcos choose not to serve us with something better are unpeople.
[1] Nothing screams "enterprise feature, call sales for pricing" like being able to run your own local hub
[2] My experience with docker is roughly: if you can write a bash script to build your environment, you can write a Dockerfile; the Dockerfile is the gateway to a system that will download 5GB of images when you really want to install 50MB of files, so what's the point? Sure, Docker accelerates your ability to have 7 versions of the JVM and 35 different versions of Python, but is that something to be proud of, really?
- maccard 2y ago> My experience with docker is roughly: if you can write a bash script to build your environment, you can write a Dockerfile I agree. > Sure, Docker accelerates your ability to have 7 versions of the JVM and 35 different versions of Python, but is that something to be proud of, really? No, but it's not my fault that the python packaging ecosystem is broken and requires isolation, and that every Java project relies on a brittle toolchain. At least docker means that nonsense is isolated and doesn't affect the stuff I write.