3 ms·
> 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
by 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.