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

["Vinod Kone (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kone updated MESOS-6874:
------------------------------
         Labels: newbie  (was: )
    Component/s: containerization

> 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
>          Components: containerization
>    Affects Versions: 1.1.0
>            Reporter: Michael Gummelt
>              Labels: newbie
>
> 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)