mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "haosdent (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-3031) Mesos should be support registry 2.0
Date Wed, 20 Jul 2016 15:50:20 GMT

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

haosdent commented on MESOS-3031:
---------------------------------

As mentioned in the ticket, there is a workaround for this
{code}
In order to solve this, you can create a tar.gz file containing the directory structure as:
tar -tvf docker.tar.gz
drwxr-xr-x root/root 0 2015-07-10 09:56 .docker/
rw------ root/root 136 2015-07-09 13:46 .docker/config.json
And add this tar file to uris. 
{code}

I think we may not support this directly in docker containerizer in the future. Because for
the registry 1.0, we add {{.dockercfg}} to uris as well.

> Mesos should be support registry 2.0
> ------------------------------------
>
>                 Key: MESOS-3031
>                 URL: https://issues.apache.org/jira/browse/MESOS-3031
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Deshi Xiao
>
> Pradeep Chhetri said on maillist:
> Hello all,
> I just wanted to share this that if you using Docker version >= 1.6 and running your
own private docker registry 2.0 and trying to deploy containers using mesos and marathon,
there might be some issues with docker registry authentication because from docker version
>=1.6, there is no .dockercfg file anymore, instead there is a .docker/config.json containing
the credentials. So docker pull will fails on mesos-slaves.
> In order to solve this, you can create a tar.gz file containing the directory structure
as:
> # tar -tvf docker.tar.gz
> drwxr-xr-x root/root         0 2015-07-10 09:56 .docker/
> -rw------- root/root       136 2015-07-09 13:46 .docker/config.json
> And add this tar file to uris. So basically when the mesos-slaves will pull inside the
containers and extract it, it will provide the correct directory structure as per docker authentication
requirements.
> Currently Mesos still only support registry 1.0, it should be better if it support registry
2.0.



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

Mime
View raw message