[PaulHoule]

Yeah but if you "don't think about what version of libc or java is in their image" either you will find out that your image cares or the programmer who comes along to maintain it will. At one job Docker seemed to give data scientists the superpower of finding a different broken Python image for every image they built, these would work OK in dev and test and then blow up in production.

My early history with Docker was terrible because it just didn't work for me because I had a slow ADSL connection and any attempt to download images would time out and fail. (I guess reliable downloads are a "call for prices" kind of feature) Later on working at an office with gigabit I found that Docker only increased build times by a factor of 2-10x depending on what I was doing.

I was wanting to build an image sorter last year and wanting to try the danbooru image board software, the git repository says just do

   docker compose

and I get a bunch of incomprehensible error messages, turns out that the compose configuration is two versions old. Could I revert compose on my system to the old version? Maybe. Probably doesn't break anything running on my machine but I'd rather not find out. Could I update the configuration file? I guess. But my internet connection still isn't that fast and I could go through a lot of run-break-fix cycles just to learn "you can't get here from there". So I cut-and-pasted the framework code out of one of my other projects and coded a minimal product up in a weekend, then had to spend another weekend adding features I tried to get away with not implementing.