Except they feel for all intents and purposes like tiny VMs. If I gave a pre-Docker era engineer two terminals, one host, one in a container, they'd probably q

Except they feel for all intents and purposes like tiny VMs. If I gave a pre-Docker era engineer two terminals, one host, one in a container, they'd probably quickly figure out they are on the same physical machine. But unless they were super savvy at some very specific stuff, they'd probably conclude it was just a VM. Every dev I've introduced to docker workflows basically treat it like a vm. The only ones that didn't already had experience with cgroups/chroot and related tools. It's honestly better to think of Docker as "VM, but actually you use the same kernel" than "processes that are isolated". Other poster compared it to electron models. Yes, "balls in orbits" is wrong, but kids are already familiar with planetary orbits, and that mental model works until basically Organic Chem II.