[jira] [Updated] (MESOS-4725) Incompatibility between Mesos and Docker - (not) picking up ~/.docker/config.json
[
https://issues.apache.org/jira/browse/MESOS-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomasz Mieszkowski updated MESOS-4725:
--
Description:
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}}
was:
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}}
> 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)
[jira] [Created] (MESOS-4725) Incompatibility between Mesos and Docker - (not) picking up ~/.docker/config.json
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)
[jira] [Commented] (MESOS-2923) fetcher.cpp - problem with certificates..?
[
https://issues.apache.org/jira/browse/MESOS-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14602855#comment-14602855
]
Tomasz Mieszkowski commented on MESOS-2923:
---
Yep, that change did the trick - thanks, Kamil! :)
@ Mesos devs - out of curiosity, what's the advantage of using
{{libcurl4-nss-dev}} instead of {{libcurl4-openssl-dev}} in {{mesos-fetcher}}..?
fetcher.cpp - problem with certificates..?
--
Key: MESOS-2923
URL: https://issues.apache.org/jira/browse/MESOS-2923
Project: Mesos
Issue Type: Bug
Affects Versions: 0.22.0, 0.22.1
Environment: Ubuntu 14.04 (build + test)
Reporter: Tomasz Mieszkowski
Mesos 0.22.0/0.22.1 built and installed from sources accordingly to the
instructions given [here|http://mesos.apache.org/gettingstarted/] has some
problem with certificates.
Every time I try to deploy something that requires downloading any resource
via HTTPS (with URI specified via Marathon), such deployment fails and I get
this message in failed app's sandbox:
{code}
E0617 09:58:44.339409 12380 fetcher.cpp:138] Error downloading resource:
Problem with the SSL CA cert (path? access rights?)
{code}
Trying to download the same resource on the same slave with {{curl}} or
{{wget}} works without problems.
Moreover, when I install exactly the same version of Mesos from Mesosphere's
debs on identical machines (i.e., set up by the same Ansible scripts),
everything works fine as well.
I guess it must be something related to the way how Mesos is built - maybe
some missing switch for {{configure}} or {{make}}..?
Any ideas..?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-2923) fetcher.cpp - problem with certificates..?
Tomasz Mieszkowski created MESOS-2923:
-
Summary: fetcher.cpp - problem with certificates..?
Key: MESOS-2923
URL: https://issues.apache.org/jira/browse/MESOS-2923
Project: Mesos
Issue Type: Bug
Affects Versions: 0.22.1, 0.22.0
Environment: Ubuntu 14.04 (build + test)
Reporter: Tomasz Mieszkowski
Mesos 0.22.0/0.22.1 built and installed from sources accordingly to the
instructions given [here|http://mesos.apache.org/gettingstarted/] has some
problem with certificates.
Every time I try to deploy something that requires downloading any resource via
HTTPS (with URI specified via Marathon), such deployment fails and I get this
message in failed app's sandbox:
{code}
E0617 09:58:44.339409 12380 fetcher.cpp:138] Error downloading resource:
Problem with the SSL CA cert (path? access rights?)
{code}
Trying to download the same resource on the same slave with {{curl}} or
{{wget}} works without problems.
Moreover, when I install exactly the same version of Mesos from Mesosphere's
debs on identical machines (i.e., set up by the same Ansible scripts),
everything works fine as well.
I guess it must be something related to the way how Mesos is built - maybe some
missing switch for {{configure}} or {{make}}..?
Any ideas..?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
