3 ms·

> Unless you use a wrong image ( like Alpine for Python) or your Dockerfile is poorly made and cache doesn't work 1. this is implementation detail. 2. it shou

> Unless you use a wrong image ( like Alpine for Python) or your Dockerfile is poorly made and cache doesn't work 1. this is implementation detail. 2. it shouldn't be so easy to write a bad Dockerfile 3. if it works, it works, and Docker encourages this approach. 4. and this damn cache: Docker is only tolerated in any way at all because of this. alternatively, it might be that baking an apple pie from scratch by first creating the universe is not the sensible thing to do. i think given the mass proliferation of Docker, i'm going to face some disagreement with this opinion: i don't think we're in a particularly good place where we have a billion deployments musl libc, busybox, nginx, and what else, all of varying versions. on top of the security implications of this, think of all the time and energy wasted in transferring all of this repeated data, on every deployment. i think it's madness.

PaulHoule 5y ago
I never got into the Docker habit because I spent a lot of time behind a slow DSL connection. Assuming it worked, I could wait a few hours to bring down an image for the the first time. Often I could get the job done in the time it takes to suck down the first image if "doing the job" could be done without Docker. I never managed to use it enough that the images were in the cache when I needed them! To make matters worse, unlike many systems that do big downloads (esp. BitTorrent) Docker is not reliable at doing large image downloads. What people don't get is that the internet infrastructure is more expensive than they think because it is paid for in bits and pieces everywhere -- for instance it is an environment disaster that console games now come in 100 GB + downloads: https://gizmodo.com/downloaded-games-have-a-larger-carbon-footprint-than-bl-1630230310 https://gizmodo.com/downloaded-games-have-a-larger-carbon-fo...

PaulHoule 5y ago

I never got into the Docker habit because I spent a lot of time behind a slow DSL connection. Assuming it worked, I could wait a few hours to bring down an image for the the first time. Often I could get the job done in the time it takes to suck down the first image if "doing the job" could be done without Docker. I never managed to use it enough that the images were in the cache when I needed them! To make matters worse, unlike many systems that do big downloads (esp. BitTorrent) Docker is not reliable at doing large image downloads. What people don't get is that the internet infrastructure is more expensive than they think because it is paid for in bits and pieces everywhere -- for instance it is an environment disaster that console games now come in 100 GB + downloads: https://gizmodo.com/downloaded-games-have-a-larger-carbon-footprint-than-bl-1630230310 https://gizmodo.com/downloaded-games-have-a-larger-carbon-fo...