Do you end up having to update multiple containers with the same patch?
Context: I've looked at Docker, but not used any containerization yet.
Do you end up having to update multiple containers with the same patch?
Context: I've looked at Docker, but not used any containerization yet.
The same way you do in any application, container or not - you look up your documentation ;)
One potential solution that came to mind was that if there was a standard way of deploying an application into containers, and Google/Amazon/Microsoft provided auto-updating containers, the maintenance of a secure container would be in the hands of companies who (hopefully) have the resources necessary to keep the entire stack up-to-date.
This in the sense, i guess, that if they have a security flaw in their php that gives disk access, all the attacker will see is the content of the php container as the database will be on the next container over.
Then again the containerization seems to have come alongside devops, where the mantra seems to be "update early, update often, to hell with stable branches".
If a security flaw exists in one container due to the stack not being updated, isn't there a pretty good chance that it also exists in the other containers?
Also, for any given container, there probably still is a way for an attacker to do immense amounts of damage. With the database container you can steal customer data. With the PHP container you can remotely instruct the database to do whatever you want, or just point the code at your own database.
All containers running code are based on these images, so the updates are picked up on the next build/deploy.
Pull a new base image, have your build system rebuild and deploy the relevant containers.
Love it for quick scripting containers (like netcat) too since it downloads in line 2 seconds.