3 ms·
There is another thing I can't get my head around. I understand containers are meant to be read only, i.e. if any binaries needs to be updated, whether in the u
by cm2187 9y ago
There is another thing I can't get my head around. I understand containers are meant to be read only, i.e. if any binaries needs to be updated, whether in the underlying image or the application, the container needs to be rebuilt from scratch.
That's all good as long as the application is actively developed. But the world is full of legacy software, actively used in production, but no longer maintained, where the source code has either been lost or no one knows how to rebuild it, or the tools to build it have become unavailable. But vulnerabilities will be found in the underlying libraries, whether it is the web server, the JVM, perhaps openssl again, or IIS for windows containers, or anything else.
How is that not going to end up as a windows server 2003-style disaster, with many many unsupported, unpatched servers all over the internet and intranets?
In fact for windows containers I understand the guest and host OS must run the very same version of the OS. How do you update or migrate your park of machines if you need the dev to re-issue all images at exactly the right time? How is that simplifying the life of ops in a large company?
- snowwrestler 9y ago> But the world is full of legacy software, actively used in production, but no longer maintained, where the source code has either been lost or no one knows how to rebuild it, or the tools to build it have become unavailable. The whole point of a container strategy is to better manage changes to the application; if the application is not changing, then containers are not needed. And it seems like a team that can't perform basic software maintenance is a team that would have trouble figuring out containers.
- organsnyder 9y agoIdeally, the CICD pipeline that generates your container images should be considered part of the running infrastructure for as long as the system is in operation. Alternatively, it's fairly painless to build a new container image with the legacy container as the base image. Containerized infrastructure is not for the faint-of-heart. If you don't have a mature CICD pipeline and associated processes—and the staff and organizational awareness to maintain them—you're going to have a bad time. You need to anticipate rebuilding your containers on at least a monthly basis due to security updates in your upstream images. Though this isn't much different than non-containerized infrastructure—your system upgrades just happen at the build phase rather than the post-deploy operations phase.