You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2018/02/08 17:32:01 UTC

[jira] [Assigned] (MESOS-7599) Mesos Containerizer Cannot Pull from Certain Registries

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

Jie Yu reassigned MESOS-7599:
-----------------------------

    Assignee: Gilbert Song

> Mesos Containerizer Cannot Pull from Certain Registries 
> --------------------------------------------------------
>
>                 Key: MESOS-7599
>                 URL: https://issues.apache.org/jira/browse/MESOS-7599
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>    Affects Versions: 1.2.0
>            Reporter: Max Ehrlich
>            Assignee: Gilbert Song
>            Priority: Major
>
> I have a docker image that is on a registry hosted by gitlab. When I try to start this container using the Mesos containerizer, it is never scheduled. I have a feeling this is from the unusual name for the image that gitlab uses, but I haven't had time to look into the code yet. I have also tried this with a private gitlab instance that is password protected and I have a similar issue (there also seems to be an unrelated issue that the Mesos containerizer doesn't support password protected registries).
> Example image names are as follows
> * registry.gitlab.com/queuecumber/page/excon (public image)
> * gitlab.<REDACTED>.com:5005/sri/registry/baseline_combo01 (private, password protected)
> The images seem to work using the Docker containerizer, and again I suspect this related to those long names with lots of / in them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)