You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Michael Gummelt (JIRA)" <ji...@apache.org> on 2017/01/06 20:08:59 UTC

[jira] [Created] (MESOS-6874) Agent silently ignores FS isolation when protobuf is malformed

Michael Gummelt created MESOS-6874:
--------------------------------------

             Summary: Agent silently ignores FS isolation when protobuf is malformed
                 Key: MESOS-6874
                 URL: https://issues.apache.org/jira/browse/MESOS-6874
             Project: Mesos
          Issue Type: Bug
    Affects Versions: 1.1.0
            Reporter: Michael Gummelt


cc [~vinodkone]

I accidentally set my Mesos ContainerInfo to include a DockerInfo instead of a MesosInfo:

{code}
executorInfoBuilder.setContainer(
                     Protos.ContainerInfo.newBuilder()
                     .setType(Protos.ContainerInfo.Type.MESOS)
                     .setDocker(Protos.ContainerInfo.DockerInfo.newBuilder()
                         .setImage(podSpec.getContainer().get().getImageName()))
{code}

I would have expected a validation error before or during containerization, but instead, the agent silently decided to ignore filesystem isolation altogether, and launch my executor on the host filesystem. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)