[
https://issues.apache.org/jira/browse/MESOS-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207637#comment-15207637
]
Gilbert Song commented on MESOS-5009:
-------------------------------------
[~jamespeach], thanks for reporting this. It is clear. We should change the way
to check `repositories` file, and avoid using JSON find here. We will fix it
soon. Pretty sure but still want to double check with you:
Are you using `docker save` to make a tarball from your private registry?
> 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
> Priority: Minor
>
> 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)
