4 ms·
Sure, but now dev has the responsibility for upgrading all those libraries again. Just because your container worked fine 5 years ago, doesn't mean it's a good
by e12e 11y ago
Sure, but now dev has the responsibility for upgrading all those libraries again. Just because your container worked fine 5 years ago, doesn't mean it's a good idea to run the same container in production today. Maybe it parses png images, or handles ssl termination.
Or you could say that ops now has the responsibility to scan all containers for old binary code/bad behaviour, and throw the container back over the fence if they find an issue.
I do agree that containers are a good start on having such a "contract" -- I'm not sure it's enough.