You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Deshi Xiao (JIRA)" <ji...@apache.org> on 2015/07/13 16:49:04 UTC
[jira] [Created] (MESOS-3031) Mesos should be support registry 2.0
Deshi Xiao created MESOS-3031:
---------------------------------
Summary: 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)