Docker images in private repos should have be accessed by the private repo's FQDN, for example:
docker.example.com/myimage:tag When pulling by this image name, it's implied that the registry is at docker.example.com and is accessible to the Docker host. It looks like the Docker module makes mention of API usernames and passwords, implying that it has the capability to authenticated against hub.docker.io and any registry that uses the index/hub authentication. I'd have to look through the source code to be sure, but I think that's what it's doing. The docker image module doens't have this capability. At any rate, check out what auth mechanism you're using on your private index, check that the docker host has access to the registry. For what it's worth, I use the docker module to work against my private registry, and it works without issue. On Sun, Jul 6, 2014 at 3:39 PM, Mark Olliver < mark.olli...@infectiousmedia.com> wrote: > Hi, > > Is there a way to pass the docker-module a set of parameters so that it > can login to a repository to download private repos. Currently I have it > downloading public ones ok but I can not get our private ones to pull. > > Thanks > > Mark > > -- > MARK OLLIVER HEAD OF IT OPERATIONS > T. +44(0) 20 7775 5628 [image: Infectious Media] 3-7 Herbal Hill / > London / EC1R 5EJwww.infectiousmedia.com [image: Infectious Media] > <http://www.infectiousmedia.com/> [image: Facebook] > <http://www.facebook.com/infectiousmedia> [image: Twitter] > <https://twitter.com/infectiousmedia> [image: LinkedIn] > <http://www.linkedin.com/company/infectious-media-ltd> [image: Youtube] > <http://www.youtube.com/user/InfectiousMediaLtd> This email and any > attachments are confidential and may also be privileged. If you are not > the intended recipient, please notify the sender immediately, and do not > disclose the contents to another person, use it for any purpose, or > store, or copy the information in any medium. Please also destroy and > delete the message from your computer. > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ansible-project+unsubscr...@googlegroups.com. > To post to this group, send email to ansible-project@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CALKPxXiL-ZfSK4zp7kR-6ZQQrYb115AQbC49h3MND-eN-v6-4A%40mail.gmail.com > <https://groups.google.com/d/msgid/ansible-project/CALKPxXiL-ZfSK4zp7kR-6ZQQrYb115AQbC49h3MND-eN-v6-4A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAK6JQEFLz%3DR6W4ROHoFdCJLF-8Z8uF5N-0FTujKtD37-y0zAxw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
