You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2018/08/28 15:45:00 UTC

[jira] [Commented] (MESOS-9185) An attempt to remove or destroy container in composing containerizer leads to segfault

    [ https://issues.apache.org/jira/browse/MESOS-9185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595174#comment-16595174 ] 

Vinod Kone commented on MESOS-9185:
-----------------------------------

What versions are affected by this bug? Should this be backported?

> An attempt to remove or destroy container in composing containerizer leads to segfault
> --------------------------------------------------------------------------------------
>
>                 Key: MESOS-9185
>                 URL: https://issues.apache.org/jira/browse/MESOS-9185
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent, containerization
>            Reporter: Andrei Budnik
>            Assignee: Andrei Budnik
>            Priority: Major
>              Labels: mesosphere
>             Fix For: 1.8.0
>
>
> `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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)