You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.
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.
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
The text was updated successfully, but these errors were encountered: