I am using OS X 10.10. When trying to communicate with our team's private docker registry, it keeps giving me errors like this:
Error: Invalid registry endpoint https://registry.xxx.xxx/v1/: Get https://registry.af-sys.com/v1/_ping: dial tcp xx.xxx.xxx.xxx:xxx: i/o timeout. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add --insecure-registry...
On Ubuntu system this error can be resolved by adding DOCKER_OPTS
into the /etc/default/docker
configuration file like this:
DOCKER_OPTS="$DOCKER_OPTS --insecure-registry myregistry:5000"
Does Mac OS have a similar configuration file where I can add the DOCKER_OPTS
option?
Enabling Insecure Registries minikube allows users to configure the docker engine's --insecure-registry flag. You can use the --insecure-registry flag on the minikube start command to enable insecure communication between the docker engine and registries listening to requests from the CIDR range.
In a typical setup where you run your Registry from the official image, you can specify a configuration variable from the environment by passing -e arguments to your docker run stanza or from within a Dockerfile using the ENV instruction. This variable overrides the /var/lib/registry value to the /somewhere directory.
I was looking for a way to set --insecure-registry
in Docker for Mac. Turned out to be simpler than what I first thought...
In the Docker Desktop application :
Don't forget to Apply & Restart and you're ready to go.
You have to set it to Docker Machine's / Boot2Docker profile file: docker-machine ssh <machine name>
/var/lib/boot2docker/profile
EXTRA_ARGS=' --label provider=virtualbox --insecure-registry myregistry:5000 '
And then restart Docker service.
sudo /etc/init.d/docker restart
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With