mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Peach (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-5009) local docker puller fails to find private registry repositories
Date Wed, 23 Mar 2016 01:10:25 GMT

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

James Peach commented on MESOS-5009:
------------------------------------

Hey Gilbert, I have a patch for this I can post pending legal review, do you mind assigning
to me?



> local docker puller fails to find private registry repositories
> ---------------------------------------------------------------
>
>                 Key: MESOS-5009
>                 URL: https://issues.apache.org/jira/browse/MESOS-5009
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization, docker
>            Reporter: James Peach
>            Assignee: Gilbert Song
>            Priority: Minor
>              Labels: container, containerizer, mesosphere
>             Fix For: 0.28.1
>
>
> If you use the unified containerizer and the local docker puller with a Docker image
from a private registry, the local puller fails to find any layers in the image's repository
manifest.
> For example, the image's {{repository}} file looks like this:
> {code}
> $  cat repositories
> {"docker-registry.foo.com/image":{"latest":"c6c35f224e926912cb61ddc48b36376c65806378432b9cbb895e10a17a99b49d"}}
> {code}
> There's 2 problems that prevent this working. First, the local puller needs to check
{{reference.registry()/reference.repository()}} as well as {{reference.repository()}}. Second,
in {{JSON::Object::find}}, the dot is treated specially so we need to just index the top level
object keys.



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

Mime
View raw message