[MESOS-5306] Mounting /etc/xxx files in CNI for command tasks has race condition.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Epic Link: filesystem isolation
• Assignee: Jie Yu
• Reporter: Jie Yu
• Created: 29/Apr/16 00:54
• Updated: 02/May/16 17:02
• Resolved: 02/May/16 17:02

Description

This is because there's no ordering between the execution of the 'isolate()' method of the CNI isolator and the execution of the preparation scripts in ContainerLaunchInfo.

For command tasks, currently, we do a recursive bind mount (<rootfs> -> <sandbox>/.rootfs) in the preparation script returned by the linux filesystem isolator (same as other volumes). The command executor will then pivot_root into <sandbox>/.rootfs.

As a result, depending on the timing. the /etc/xxx files mounted at <rootfs>/etc/xxx might or might not be present in the rootfs for command tasks.

Issue Links

• relates to: MESOS-5307 Sandbox mounts should not be in the host mount namespace.