Chapter 14. Containers Aren’t Magic
Katie McLaughlin
Containers, and the Open Container Initiative (OCI) image format specifications, aren’t magic cure-alls. Popularized by Docker in the mid-2010s, the concept of having a definition create an isolated space for software to live in isn’t unique and isn’t a panacea.
Isolation standards have existed for years: virtual machines (VMs) are an isolation mechanism. Your VM may not touch your neighbor’s VM, unless you specifically allow it to (typically, through network firewalls). However, that doesn’t mean you can’t have vulnerable software and malicious programs on your system.
Containers can be seen as just an iteration on VMs, but in a smaller form factor. VMs allowed more isolation environments on bare-metal servers. Containers serve the same purpose, and are vulnerable to the same issues as VMs. Indeed, Docker itself has been shown to be reproducible in a mere 100 lines of bash. The mechanisms by which we achieve isolation are not unique or new, and the advantages they give us don’t outweigh the considerations we need to keep in mind.
Downloading a random executable from the internet without knowing what it does and running it on your local machine is something that should cause a tickle in the back of any programmer’s head. So why would you include a FROM in your Dockerfile without knowing the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access