[MESOS-9185] An attempt to remove or destroy container in composing containerizer leads to segfault.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Fix Version/s: 1.7.0
• Component/s: agent, containerization
• Labels: mesosphere
• Target Version/s: 1.7.1, 1.8.0
• Sprint: Mesosphere Sprint 2018-27
• Story Points: 3
• Assignee: Andrei Budnik
• Reporter: Andrei Budnik
• Shepherd: Alex R
• Created: 27/Aug/18 15:11
• Updated: 04/Sep/18 21:47
• Resolved: 28/Aug/18 14:49

Description

`LAUNCH_NESTED_CONTAINER` and `LAUNCH_NESTED_CONTAINER_SESSION` leads to segfault in the agent when the parent container is unknown to the composing containerizer. If the parent container cannot be found during an attempt to launch a nested container via `ComposingContainerizerProcess::launch()`, the composing container returns an error without cleaning up the container. On `launch()` failures, the agent calls `destroy()` which accesses uninitialized `containerizer` field.