Re:CoreOS Overview, Part One
by frik on Saturday January 30, 2016 @01:04AM
(#11000756)
This. With other sandbox container solutions, you just start it. Docker's is mixing a sandbox, a deployment solution and more together. This might be useful for large deployments, but for smaller one it's too complex.
[ Parent
| on HN ]
for sandboxes you don't need containers and for resource management, neither. The only thing which docker gives you, is that it enforces immutable disks, which cgroups can't do, can't yet do or whatever.
however when even with docker you need to ensure that your program won't mutate the filesystem so anyways nothing special.
Re:CoreOS Overview, Part One
by icebraining on Saturday January 30, 2016 @05:43AM
(#11001410)
Enforcing an immutable filesystem is actually pretty easy to do, just don't give write permissions to the user under which the program is running :)
What Docker integrates is a layered filesystem, in which the application can mutate the filesystem, but only it will see those changes (and they'll go away when the container is destroyed).
Re:CoreOS Overview, Part One
by justincormack on Saturday January 30, 2016 @07:20AM
(#11001596)
You can mount the base filesystem read only in the container as of 1.10, with tmpfs mounts for where you need ephemeral mutation.