Clever Geek Handbook

How to fix insecure-registry error on clients by updating the docker registry server

When upgrading to docker 1.3, the docker client produced the following error:

... 
If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry <my registry>` to the daemon arguments.
...

This registry is behind our company's firewall, so I don't want to add any security. Is there a way to remove this error on the registry server? What's the easiest way to do this? Does https include or is there an easier trick?

I don't want to update config for all registry clients

+3


source to share


1 answer


You must use https if you want to avoid this warning. You also need a certificate signed by a well-known CA. Docker tries to keep things safe with this.



Another possibility is to use --insecure-registry

when using the client.

+1


source






More articles:


All Articles