We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitLab's runner utilizes a DOCKER_AUTH_CONFIG environment variable to access private registries at the job or runner level.
DOCKER_AUTH_CONFIG
The variable is some escaped JSON that follows Docker's login config format which looks like:
{ "auths": { "registry.example.com:5000": { "auth": "bXlfdXNlcm5hbWU6bXlfcGFzc3dvcmQ=" } } }
…where auths.[reg].auth is base64 encoded basic auth values (i.e., USER:PASS).
auths.[reg].auth
USER:PASS
So we could match image registries to the keys in the auths object, decode the base64 then split on the colon and supply to cf push.
auths
cf push
The text was updated successfully, but these errors were encountered:
No branches or pull requests
GitLab's runner utilizes a
DOCKER_AUTH_CONFIG
environment variable to access private registries at the job or runner level.The variable is some escaped JSON that follows Docker's login config format which looks like:
…where
auths.[reg].auth
is base64 encoded basic auth values (i.e.,USER:PASS
).So we could match image registries to the keys in the
auths
object, decode the base64 then split on the colon and supply tocf push
.The text was updated successfully, but these errors were encountered: