Docker pull not using correct DNS server when private registry on VPN

[jessesuen]

The next problem you will likely run into after fixing DNS issues, is that your private registry is untrusted and does not have a signed certificate. To get past this:

Edit /etc/init.d/docker and add --insecure-registry <registry_hostname> to the DOCKER_OPTS line.

Credit goes here:

Running an insecure registry --insecure-registry

ya you’re correct, https://docs.docker.com/engine/reference/commandline/daemon/#daemon-configuration-file has a list of variables available to the .json config file. Anything else is ignored. i was able to modify /etc/init.d/docker (by opening a console to the linux machine: screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty) on line 39: DOCKER_OPTS="${DOCKER_OPTS} -H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock --insecure-registry some.domain.here" and…