When running a registry, its essential to make sure your clients can access it easily and securely.

If your registry isnt running on a public domain, youre probably using a self-signed certificate for this purpose.

This post will look into some of the issues around accessing registries with self-signed certificates from clients, including Docker for Mac.

The above solution doesnt work, as Docker for Mac relies on a internal VM whose filesystem gets wiped on restarts.

The correct solution (thanks to Justin Cormack ) is to add the certificate to the Macs keychain, which will be picked up by Docker for Mac e.g.

In addition it can automatically set-up a secure registry on Kubernetes, which will be the topic of a later post.

Which breaks SSL and makes containers kind-of strange to work with.

Does require you to build on all images with your own though.

As commented above, I think you would want to build a new image with a custom Dockerfile (using the image you pulled as a base image), ADD your certificate, then RUN update-ca-certificates.

On the next docker run -d any other options IMAGEID, the container started by that command will have your certificate info.

But your solution also works if you need certificates during docker build.

Someone else could pull your container and extract your private certs.

This is meant to add your own certificates into an image that is built locally and then used privately.

You could then push the resulting image to a public repository, but that would be a bad idea as you said.

Kinda great for local development and keep the certs folder visible to your project.

Making statements based on opinion; back them up with references or personal experience.

Not the answer youre looking for Browse other questions tagged ssl ssl-certificate docker or ask your own question.

Docker For Mac Certificates Folder