If you’re using Docker Toolbox, then THIS article solved it for me: https://github.com/boot2docker/boot2docker#insecure-registry
When essentially you install the certificates to your docker machine, instead of to your Windows installation.
Generate certs (I use the Docker Quickstart Terminal)
1 |
openssl s_client -connect hki-repo03.xxx.com:8222 |
Take bit of output from “BEGIN CERTI” to “END CERT” INCLUSIVE*, and copy to “ca.crt”, e.g.
—–BEGIN CERTIFICATE—–
MIIC6TCCAlICCQDjDRoI8gkx1TANBgkqhkiG9w0BAQUFADCBuDELMAkGA1UEBhMC
RkkxFjAUBgNVBAgMDUhlbHNpbmtpIEFyZWExETAPBgNVBAcMCEhlbHNpbmtpMRww
GgYDVQQKDBNDb21wdGVsIENvcnBvcmF0aW9uMRQwEgYDVQQLDAtJVCBTZXJ2aWNl
czEfMB0GA1UEAwwWaGtpLXJlcG8wMy5jb21wdGVsLmNvbTEpMCcGCSqGSIb3DQEJ
ARYaU3RveWFuLkFuZ2Vsb3ZAQ29tcHRlbC5DT00wHhcNMTYwMzEyMDk1MzAxWhcN
MTcwMzEyMDk1MzAxWjCBuDELMAkGA1UEBhMCRkkxFjAUBgNVBAgMDUhlbHNpbmtp
IEFyZWExETAPBgNVBAcMCEhlbHNpbmtpMRwwGgYDVQQKDBNDb21wdGVsIENvcnBv
cmF0aW9uMRQwEgYDVQQLDAtJVCBTZXJ2aWNlczEfMB0GA1UEAwwWaGtpLXJlcG8w
My5jb21wdGVsLmNvbTEpMCcGCSqGSIb3DQEJARYaU3RveWFuLkFuZ2Vsb3ZAQ29t
cHRlbC5DT00wgZ8wDQYJKoZIhvcNAQEBasdasdasQADgY0AMIGJAoGBAKdbrtYFjWugtG9u
VfqGkkR+i8q188MSfrFKE4Wzr0m7f3wasdlSsMx08Tv5C+U56z2zmlsojvBJFHY9k
D6b1V5WRtC2suysF5v/7bqsM1xdsadaRmavYU0rBhsaGaOLZ1d3Q3RkWIlKexShNc30R
LOXwf0FO0II4l1ltnNsq7LutasdasdAgMBAAEwDQYJKoZIhvcNAQEFBQADgYEAY/4V
udI6NItfUFdJoq3aiQ/qIsMiP0w1DutjgFe0l5bgObvt+Lo/lLQKxhKLy+whdhje
F2jETrm5Ti5bLLoFbPdGaaSFTboMmP/wjAyGOOtGv3xcKxc7zAa9SDgq4T6G1u5z
sMi+tXN0mv0HVpZ2CdSBKJ271FPSWWebYZnXY1E=
—–END CERTIFICATE—–
Then run the following on Windows:
1 2 3 4 5 6 |
docker-machine scp ca.crt default:ca.crt docker-machine ssh default sudo mkdir /etc/docker/certs.d/hki-repo03.xxx.com:8222/ sudo mv ~/ca.crt /etc/docker/certs.d/hki-repo03.xxx.com:8222/ca.crt exit docker-machine restart |
After that, the following said “login succeeded”
1 |
docker login login hki-repo03.xxx.com:8222 |