I am on a trial of the DTR in AWS. Since it is a trial I don’t have a certificate yet.
When I tried this with a custom private registry I simply added
to /etc/sysconfig/docker. This does not seem to work with the DTR. Based on other posts I also tried to add
to /etc/default/docker but it does not help either.
This is the detailed error I get when try to login before a push:
Error response from daemon: invalid registry endpoint https://172.x.x.x/v0/: unable to ping registry endpoint https://172.x.x.x/v0/ v2 ping attempt failed with error: Get https://172.x.x.x/v2/: x509: cannot validate certificate for 172.x.x.x because it doesn't contain any IP SANs v1 ping attempt failed with error: Get https://172.x.x.x/v1/_ping: x509: cannot validate certificate for 172.x.x.x because it doesn't contain any IP SANs. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry 172.x.x.x` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/172.x.x.x/ca.crt
Am I missing something or is it a DTR problem?