Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
(Wildcard?) Registry certificate CA issues OSX / Virtualbox #805
I know I must be missing something obvious, but I cannot docker login to a private registry using a non-standard (wildcard, Comodo EssentialSSL) SSL/TLS certificate.
I installed boot2docker & Virtualbox via the OSX Boot2Docker-1.5.0.pkg installer.
[Also: I know these files will be blown away on reboot. My goal was to get it working then get it repeatable, however if there is a better way to solve both issues simultaneously, I’d love to know]
All of the solutions I can find online are either A) for a debian VM/host, B) dangerously tell the user to just turn off SSL certificate validation with
I have placed the Comodo EssentialSSL CA bundle in the appropriate location and it does not seem to help.
That’s to be expected. However, after I add the CA bundle, I get a pruned error message (interestingly with a different error code):
Just to confirm the bundle is correct, curl is happy to use it:
Without the CA bundle:
And with it:
So that suggests to me that the bundle is not incorrect, but I am at a loss for where to go next.
Did you try pointing at a copy of your CA cert file with
Thanks for your replies. I don’t think the cross-compilation is to blame, since all of the commands above were run inside the boot2docker VM. But still, it’s good to know that could be an issue.
I’ll go read the threads you linked and see if I can find a suitable workaround. Thanks.
Complicating matters is that I’m running boot2docker in virtualbox to build a generic solution for the rest of the company. I have both CentOS 7 & boot2docker running in Parallels VMs configured via Vagrant, and neither one exhibits this behavior. It’s maddening!
(This is why I posted an issue in this repo: it seems specific to the specific boot2docker install)