Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
1.1.0
-
Mesos Foundations RI12 Sp 42
-
5
Description
cc vinodkone
I accidentally set my Mesos ContainerInfo to include a DockerInfo instead of a MesosInfo:
executorInfoBuilder.setContainer( Protos.ContainerInfo.newBuilder() .setType(Protos.ContainerInfo.Type.MESOS) .setDocker(Protos.ContainerInfo.DockerInfo.newBuilder() .setImage(podSpec.getContainer().get().getImageName()))
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.
Attachments
Issue Links
- causes
-
MESOS-9740 Invalid protobuf unions in ExecutorInfo::ContainerInfo will prevent agents from reregistering with 1.8+ masters
- Resolved
- links to