[MESOS-5931] Support auto backend in Unified Containerizer.

• Type: Improvement
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Component/s: containerization
• Labels: backend containerizer mesosphere
• Target Version/s: 1.2.0
• Epic Link: Unified Container
• Sprint: Mesosphere Sprint 41, Mesosphere Sprint 42, Mesosphere Sprint 47, Mesosphere Sprint 48, Mesosphere Sprint 49, Mesosphere Sprint 50
• Story Points: 8
• Assignee: Gilbert Song
• Reporter: Gilbert Song
• Shepherd: Jie Yu
• Created: 29/Jul/16 18:10
• Updated: 21/Feb/17 23:29
• Resolved: 29/Jan/17 22:23

Description

Currently in Unified Containerizer, copy backend will be selected by default. This is not ideal, especially for production environment. It would take a long time to prepare an huge container image to copy it from the store to provisioner.

Ideally, we should support `auto backend`, which would automatically/intelligently select the best/optimal backend for image provisioner if user does not specify one from the agent flag.

We should have a logic design first in this ticket, to determine how we want to choose the right backend (e.g., overlayfs or aufs should be preferred if available from the kernel).

Issue Links

• depends upon: MESOS-6001 Aufs backend cannot support the image with numerous layers.
• depends upon: MESOS-6653 Overlayfs backend may fail to mount the rootfs if both container image and image volume are specified.
• depends upon: MESOS-6654 Duplicate image layer ids may make the backend failed to mount rootfs.
• depends upon: MESOS-6958 Support linux filesystem type detection.
• is related to: MESOS-7154 Document provisioner auto backend support.
• relates to: MESOS-6000 Overlayfs backend cannot support the image with numerous layers.