mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Downes" <>
Subject Re: Review Request 34427: AppC provisioner backend using bind mounts.
Date Mon, 22 Jun 2015 16:53:37 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated June 22, 2015, 9:53 a.m.)

Review request for mesos, Chi Zhang, Paul Brett, Timothy Chen, and Vinod Kone.


Minor code changes to address comments.

Repository: mesos


Note: This is a specialized backend; see notes in bind_backend.hpp.
Reproduced here for your convenience:

This is a specialized backend that may be useful for deployments
using large (multi-GB) single-layer images *and* where more
recent kernel features such as overlayfs are not available. For small
images (10's to 100's of MB) the Copy backend may be sufficient.
1) It supports only a single layer. Multi-layer images will fail
   to provision and the container will fail to launch!
2) The filesystem is read-only because all containers using this
   image share the source. Select writable areas can be achieved
   mounting read-write volumes to places like /tmp, /var/tmp,
   /home, etc. using the ContainerInfo. These can be relative to
   the executor work directory.
3) It relies on the image persisting in the store.
4) It's fast because the bind mount requires (nearly) zero IO.

Diffs (updated)

  src/ e7de0f3d1a5efeaef47d5074defe3b40db94f573 
  src/slave/containerizer/provisioners/appc/backend.cpp PRE-CREATION 
  src/slave/containerizer/provisioners/appc/bind_backend.hpp PRE-CREATION 



manual testing of a single layer image with RW relative bind mount for /tmp.


Ian Downes

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message