[jira] [Created] (MESOS-4725) Incompatibility between Mesos and Docker - (not) picking up ~/.docker/config.json

["Tomasz Mieszkowski (JIRA)" <ji...@apache.org>]

Tomasz Mieszkowski created MESOS-4725:
-----------------------------------------

             Summary: Incompatibility between Mesos and Docker - (not) picking up ~/.docker/config.json
                 Key: MESOS-4725
                 URL: https://issues.apache.org/jira/browse/MESOS-4725
             Project: Mesos
          Issue Type: Bug
            Reporter: Tomasz Mieszkowski


Having Mesos 0.23.1 and Docker 1.7.1, I can put my auth token for my private registry (Artifactory) into {{/root/.docker/config.json}} on every slave node, and when I'm deploying my dockerized app to Mesos via Marathon it works fine (i.e., this auth token is picked up by Docker and images are pulled successfully).

But when I use Mesos (1) and Docker >= 1.8.3 (2), this mechanism doesn't work anymore (i.e., for some reason {{/root/.docker/config.json}} is ignored, and therefore Docker is unable to pull images from the same location as above).

What makes it interesting, is the fact that when I run the same command as Mesos (3) from the root's shell, directly on any slave node, it works as expected (i.e., images are pulled successfully), so this clearly is not Docker's fault.

Any ideas what it may be..?

(1) - Tested with Mesos 0.23.1, 0.24.1, 0.25.0, 0.26.0 and 0.27.0.
(2) - Tested with Docker 1.7.1, 1.8.3 and 1.9.1.
(3) - {{docker -H unix:///var/run/docker.sock pull my.private_registry.com/xxx/my_image:latest}}



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