Closed bacongobbler closed 8 years ago
Wonder if it has to do with the fact there is no hostname on it and Kubernetes gets confused
Can you verify that the secret is written out properly and the base64 does contain everything you need?
Is this what you need?
@jdumars yeah, does that match with what you have in your local .docker/
config?
there isn't a local docker installation on this box -- is that a requirement?
No, but docker
makes the same type of file / structure locally when you do docker login
or similar. It's a good way to see if things are being created right
FYI I noticed there was a new command called kubectl create secret docker-registry
, and when I tried to create that manually the two resultant docker configs seem to differ. More specifically, the one we generate is of type kubernetes.io/dockerconfigjson
and the one generated with kubectl create secret docker-registry
created a secret of type kubernetes.io/dockercfg
, and the resultant hashes differed as well as the keys (.dockercfg
and .config.json
, IIRC).
kubectl --namespace=bar create secret docker-registry my-secret --docker-username=jsingerdumars --docker-password="******" --docker-email="jsingerdumars@gmail.com"
Yeah, but you can create both. .dockercfg
is just the old config format for Docker
Given a private image hosted at DockerHub with Workflow v2.2.0, @jdumars and I cannot seem to be able to get Workflow to pull it down.
The
private-registry
secret is created, however this is the error in the controller:However, this image does indeed exist because if we
docker login
locally and pull it,docker pull
works just fine.Quay seems to work because I tested with the e2e credentials in https://github.com/deis/workflow-e2e/blob/07509ad1c2f5e21ef4e4c9c9b98e0c42578af1d4/tests/registry_test.go#L102-L115 and that worked fine.
CC @jdumars