Re:Technical debt as an opportunity to accumulate technical ...
by lallysingh on Monday August 15, 2016 @04:04PM
(#12292993)
Yes, yes they are.
And they're written down where you can read them yourself. And maybe even version controlled!
Re:Technical debt as an opportunity to accumulate technical ...
by GrinningFool on Monday August 15, 2016 @05:25PM
(#12293587)
On the other hand, tracing back a dockerfile that pulls in an obscure one-off base image, then repeating that all the way up the chain, you can find yourself left with a dozen Dockerfiles that you need to read in the right order to know what you have.
That's if you can even find the original Dockerfiles - I recently ran into a situation where a container image was in the registry, but the original Dockerfile was completely lost.
Docker/containers in general move the complexity to a different plane, but they only move it - they don't eliminate it. Care needs to be taken to avoid situations just like the one above - or any of a number of other pitfalls - or you end up with an environment that's far more complex to understand than a VM housing a monolithic dev environment.
In that case, wouldn't the Dockerfile be a relatively transparent way to see what's needed to reproduce an environment?