HTTPS requests in a container don't work

[meyay (Metin Y.)]

Those are two different layers: of course it is possible to add the ca certificate used by TLS inspection to the docker demon. As TLs inspection breaks the security context to the registry, you will need to treat it like a secure private registry:

@https://docs.docker.com/engine/reference/commandline/dockerd/#insecure-registries

A secure registry uses TLS and a copy of its CA certificate is placed on the Docker host at /etc/docker/certs.d/myregistry:5000/ca.crt. An insecure registry is either not using TLS (i.e., listening on plain text HTTP), or is using TLS with a CA certificate not known by the Docker daemon. The latter can happen when the certificate was not found under /etc/docker/certs.d/myregistry:5000/, or if the certificate verification failed (i.e., wrong CA).

Note: myregistry:5000 is just an example fqdn for a private registry.

The ca.crt used by the tls inspection must be placed in /etc/docker/certs.d/{fqdn of the registry}/ca.crt
I don’t recall whether the docker demon needs to be restarted to actually use the certificate.

On Docker Desktop for Mac the solution can be found in the faqs: https://docs.docker.com/desktop/faqs/macfaqs/#how-do-i-add-tls-certificates

@naikrovekwork

Is there a way to tell Docker about this without modifying containers?

I assume you mean the image, as it would be tedious to inject the certificates manually into each container.

Update: fixed a wrong wording