4 ms·
To me it's more like a lightweight virtualization: processes inside containers have no clues that there are others processes running in others containers alongs
by bpizzi 10y ago
To me it's more like a lightweight virtualization: processes inside containers have no clues that there are others processes running in others containers alongside its own, all of that without eating too much memory (at least well under the amount that virtual machines would use).
Added benefits:
- the 'host' os can be very light and tailored to run Docker and nothing more (cf CoreOS),
- we can design orchestration software that handle containers operations across a herd of lightweight hosts (cf Kubernetes).
The dependencies/recipes thing is more like a tool that enable those higher goals, but again that's just my point of view.
- majewsky 10y ago> processes inside containers have no clues that there are others processes running in others containers alongside its own Except, of course, if you're dealing with privileged containers. Docker [1] gives you detailed control over what to share between container and host, and what to isolate (with the default being more rather than less isolation). For example, I'm currently working on a container that mounts disks in the host's mount namespace. In that case (and many others), the selling point of Docker [1] is not the isolation, but the deployment story. [1] Or any other container runtime. I'm saying "Docker" because that's the one I'm familiar with.