You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jan Schlicht (JIRA)" <ji...@apache.org> on 2016/09/21 09:54:20 UTC

[jira] [Commented] (MESOS-6209) Containers that use the Mesos containerizer but don't want to provision a container image fail to validate.

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

Jan Schlicht commented on MESOS-6209:
-------------------------------------

Looks like JIRA created this ticket twice. MESOS-6208 is the canonical ticket.

> Containers that use the Mesos containerizer but don't want to provision a container image fail to validate.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-6209
>                 URL: https://issues.apache.org/jira/browse/MESOS-6209
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>         Environment: Mesos HEAD, change was introduced with e65f580bf0cbea64cedf521cf169b9b4c9f85454
>            Reporter: Jan Schlicht
>
> Tasks using  features like volumes or CNI in their containers, have to define these in {{TaskInfo.container}}. When these tasks don't want/need to provision a container image, neither {{ContainerInfo.docker}} nor {{ContainerInfo.mesos}} will be set. Nevertheless, the container type in {{ContainerInfo.type}} needs to be set, because it is a required field.
> In that case, the recently introduced validation rules in {{master/validation.cpp}} ({{validateContainerInfo}} will fail, which isn't expected.



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