![]() The correct solution (thanks to Justin Cormack) is to add the certificate to the Mac's keychain, which will be picked up by Docker for Mac e.g: The above solution doesn't work, as Docker for Mac relies on a internal VM whose filesystem gets wiped on restarts. With the Mac, however, things are a little different. Sudo cp ca.crt /etc/docker/certs.d/test-docker-reg\:5000/ ![]() ![]() Sudo mkdir /etc/docker/certs.d/test-docker-reg\:5000 This post will look into some of the issues around accessing registries with self-signed certificates from clients, including Docker for Mac.ĭistributing certificates to Linux Docker clients is pretty straightforward, as it just means copying the certificate to the correct directory (for the purposes of this post, I'm assuming you know how to create a self-signed cert for the registry): If your registry isn't running on a public domain, you're probably using a self-signed certificate for this purpose. When running a registry, it's essential to make sure your clients can access it easily and securely. The Docker registry image has over 10 million pulls on Docker Hub, so it's safe to say that a lot of people out there are making use of it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |