3 ms·

This has always been my hesitation with Docker— unless you have a proper pipeline in place to be constantly rebuilding your overlay from updated versions of the

This has always been my hesitation with Docker— unless you have a proper pipeline in place to be constantly rebuilding your overlay from updated versions of the base image, you're basically just carrying a snapshot of unknown binaries into the future with you, indefinitely. Obviously, any reasonable shop will have such a pipeline in place, but DockerHub and the whole ecosystem of docker getting started tutorials seem to really encourage a "set it and forget it" mentality toward a container once it's built and working.

orf 8y ago
Do they? The whole point is you'd rebuild your app every redeploy, which includes from the base image. Docker has a lot of problems but build repeatability is not one of them, in my experience. It makes it really really frictionless, in some cases way too frictionless
duxup 8y ago
As someone just getting a feel for Docker I keep thinking: "Wait what is all th---" And then the tutorials or documentation just rolls on.... and doesn't really get back to what I should be doing to maintain / secure anything.