Skip to content
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.

How to configure logins for private registries? #3299

Closed
pschultz opened this issue Apr 12, 2016 · 3 comments
Closed

How to configure logins for private registries? #3299

pschultz opened this issue Apr 12, 2016 · 3 comments

Comments

@pschultz
Copy link
Contributor

I haven't found a way yet to configure credentials for our private registry (as in username and password, TLS is working fine).

I expected docker-machine to copy $HOME/.dockercfg to the VMs (like it copies certificates).

Am I missing something or are login credentials for private registries not supported?

@nathanleclaire
Copy link
Contributor

They're supported but it's always read from the computer where the Docker client is invoked AFAIK. So, if you want to pull private images, you need to docker pull from the same computer (client) where you have already docker logined.

@nathanleclaire
Copy link
Contributor

If desired, you could docker-machine scp the .dockercfg file to your created instances.

@pschultz
Copy link
Contributor Author

We want to use Gitlab's new autoscale feature for continuous integration, which uses docker-machine to launch instances on demand. The gitlab-ci runner doesn't provide an opportunity to provision VMs.

Currently I don't see an alternative to building custom images for each cloud provider we want to try, which is annoying and time consuming at best and a security risk at worst.

docker-machine is already copying TLS certificates, so I'd argue it should do the same with the login credentials.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants