4 ms·
Yeah, it seems like there's a weird inbetween phase when projects go from "awesome tool used and loved by some core people" to "this is the new normal, it's eve
by qbasic_forever 5y ago
Yeah, it seems like there's a weird inbetween phase when projects go from "awesome tool used and loved by some core people" to "this is the new normal, it's everywhere" where these issues get lost. I could see back in 2014 moby not really feeling like the quirks of ufw & iptables were its problem. But now in 2021 with how many millions of times docker run is used per day on machines all across the internet... it's just irresponsible security. It sucks, it isn't really docker's problem in the first place... but it's reality and someone needs to grab the hot potato and keep it from burning people for the good of us all.
- jbrot 5y agoI know the CICD code I wrote and manage at work launches approximately a million docker containers a day, so I suspect the total number of docker containers used per day is well into the billions.
- mafro 5y agoDo tell about where you would need a million docker images for a CICD pipeline.. It's either many apps, or some very complicated pipelines
- zbentley 5y agoOr many builds of the same app. Think compatibility matrix testing: take one suite of tests and run them against every one of hundreds of permutations of versions of their dependencies, one container each. Not GP, just hypothesizing. This is what Travis matrixes do, for example.
- jbrot 5y agoWe have a suite of about two thousand integration tests and we run each test in its own docker container for isolation purposes. Multiply by 500 jobs a day and you get to a million containers.
- gnyman 5y agoI agree, there is a huge difference what one should expect from a early OS project and what one should be able to expect from billion dollar companies. But it seems that without external pressure (regulatory?), it's not getting fixed at either end.