docker service create doesn't find image

When I run docker service create –mode global foo myrepo/foo-img:0.1, it works in that it starts the service, but if foo-img:0.1 does not exist on a node in the swarm, that node emits the following error:

<containerid>   \_ foo    myrepo/foo:0.1  <snip>  "No such image: myrepo/foo-img:0.1"

If I pull myrepo/foo-img:0.1 on each node then it works fine.

  • Container exits if invoked from compose
  • Docker container with licensed software
  • chef-container + chef-vault
  • curl: (7) Failed to connect to localhost port 8090: Connection refused
  • Development workflow on Minikube and docker
  • Add additional ip's to lo interface in docker container
  • Is there a workaround for this other than pulling the image on each node in the swarm?

  • Docker not mounting host files
  • ARG or ENV, which one to use in this case?
  • How to change working of top command
  • How can I create a docker image from the current system?
  • How to run a Windows GUI application from a Windows VM on a Docker installed on windows?
  • There is a way to ping a Docker container using its hostname, from another Docker Container?
  • One Solution collect form web for “docker service create doesn't find image”

    The answer is actually pretty simple. Use the--with-registry-auth parameter. This parameter uses the same authentication that is used for your current session. So, to make this work you simply:

    # docker login -u xxx -pass yyy
    # service create --with-registry-auth foo

    Assuming that you successfully logged in, the service will pull the image from the repo to each node as needed. Not sure exactly what happens behind the scenes, but it works for deploying to all nodes currently in the cluster! Thanks to the help from the folks at github/docker!

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.