mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Rukletsov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-6208) Containers that use the Mesos containerizer but don't want to provision a container image fail to validate.
Date Tue, 20 Sep 2016 15:02:21 GMT

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

Alexander Rukletsov updated MESOS-6208:
---------------------------------------
         Assignee: Alexander Rukletsov
           Sprint: Mesosphere Sprint 43
     Story Points: 1
           Labels: mesosphere  (was: )
    Fix Version/s: 1.1.0

> Containers that use the Mesos containerizer but don't want to provision a container image
fail to validate.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-6208
>                 URL: https://issues.apache.org/jira/browse/MESOS-6208
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>         Environment: Mesos HEAD, change was introduced with e65f580bf0cbea64cedf521cf169b9b4c9f85454
>            Reporter: Jan Schlicht
>            Assignee: Alexander Rukletsov
>              Labels: mesosphere
>             Fix For: 1.1.0
>
>
> 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)

Mime
View raw message