[ https://issues.apache.org/jira/browse/MESOS-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796412#comment-16796412 ]
Benno Evers commented on MESOS-6874: ------------------------------------ {noformat} commit 93aca1eb0efcec941e19e976f683a35ecd9a840b Author: Andrei Sekretenko <asekrete...@mesosphere.com> Date: Tue Mar 19 18:55:55 2019 +0100 Validated the match between Type and *Infos in the ContainerInfo. [...] {noformat} > 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 > Assignee: Andrei Sekretenko > Priority: Minor > Labels: foundations, newbie > Time Spent: 40m > Remaining Estimate: 0h > > 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 (v7.6.3#76005)