[
https://issues.apache.org/jira/browse/MESOS-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103064#comment-15103064
]
Timothy Chen commented on MESOS-4391:
-------------------------------------
Concurrent pulling the same image is handled by the docker daemon and doesn't
require any special synchronization on our side. We only need to handle cases
where either the docker daemon doesn't handle, or certain load / pattern that
will break. AFAIK it's just a warning that shows up in the daemon side and from
the client side everything still works.
> docker pull a remote image conflict
> -----------------------------------
>
> Key: MESOS-4391
> URL: https://issues.apache.org/jira/browse/MESOS-4391
> Project: Mesos
> Issue Type: Bug
> Components: docker, framework
> Affects Versions: 0.26.0
> Environment: CentOS Linux release 7.2.1511 (Core)
> 3.10.0-327.el7.x86_64
> Reporter: qinlu
>
> I run a docker app with 3 tasks,and the docker image not exist in the slave
> ,it must to pull from docker.io.
> Marathon assign 2 app run in a slave,and the last in another.
> I see the log by journalctl,it show me like this :level=error msg="HTTP
> Error" err="No such image: solr:latest" statusCode=404.
> There is two threads to pull the image
> [root@** ~]# ps -ef|grep solr
> root 30113 10735 0 12:17 ? 00:00:00 docker -H
> unix:///var/run/docker.sock pull solr:latest
> root 30114 10735 0 12:17 ? 00:00:00 docker -H
> unix:///var/run/docker.sock pull solr:latest
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
