--Hi,Vivek Goyal (cc) and I were discussing ways to deliver page cache sharing, POSIX compliance and SELinux support with a single docker graph driver, using existing kernel facilities. We decided to go with a bind-mount technique, and Vivek has posted a first cut here: https://github.com/docker/
docker/pull/27364Testing of the prototype looks like a great improvement:http://developerblog.redhat. com/2016/10/25/docker-project- can-you-have-overlay2-speed- and-density-with-devicemapper- yep/Assuming this type of feature is merged in a container run-time, what preference would Kube folks have for surfacing this to users ... currently it's a daemon runtime flag that says ... if you use --read-only then you get the shared-rootfs as well. Obviously this requires "12factor-ish" design up front, because you can no longer scribble in the container filesystem in places that are not persistent volumes, but we think read-only container hygiene is well worth the security and performance improvements to be had.
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@
To post to this group, send email to kubernetes-dev googlegroups
To view this discussion on the web visit https://groups.google.com/d/
msgid/kubernetes-dev/CABxNGQa-. VLzP%3DEFYQucfJtTEtSHmWac4Tv% 3Dc%2BQVAFJNcDLSb1g%40mail. gmail.com
For more options, visit https://groups.google.com/d/