> Give up the idea of data volume containers. Given that volumes are the way to go, no other filesystems in the container need to, or should be, writable. Inte

> Give up the idea of data volume containers. Given that volumes are the way to go, no other filesystems in the container need to, or should be, writable. Interesting philosophy, it will pose some issues when replicating a Docker 'build' like system though. But that could be separated from the 'run' system with cached layers. edit: Btw, Docker also seems to support this: https://nickjanetakis.com/blog/docker-tip-55-creating-read-only-containers https://nickjanetakis.com/blog/docker-tip-55-creating-read-o.... Also allowing explicit creation of writable tmpfs mountpoints.