After reviewing this with the team again, we noticed the CA certificate is configured by docker and Engine don't touch to this configuration. We found out that this is already configurable with Docker desktop. See:
check out AWS_CA_BUNBLE from AWS CLI for inspiration. I have a lambda hitting a secure site. to locally invoke it using SAM (which runs in Docker), I had to create a PEM file containing the certificates, copy it to the package, reference that parameter in the CFT and pass it a value thru the invocation command
Cyril Kazmierczak
Cyril, currently this is not planned in the near term. But we'll keep this in future consideration to see the interest in this feature.
The request is not about connecting to a registry but for code running inside a container to make secure requests to external APIs
Hi Cyril,
After reviewing this with the team again, we noticed the CA certificate is configured by docker and Engine don't touch to this configuration. We found out that this is already configurable with Docker desktop. See:
https://docs.docker.com/desktop/mac/#add-tls-certificates
https://docs.docker.com/desktop/windows/#adding-tls-certificates
check out AWS_CA_BUNBLE from AWS CLI for inspiration. I have a lambda hitting a secure site. to locally invoke it using SAM (which runs in Docker), I had to create a PEM file containing the certificates, copy it to the package, reference that parameter in the CFT and pass it a value thru the invocation command
Hi Cyril,
Thanks for submitting this idea. We have reviewed the use case and it makes sense. We'll plan in future CLI releases.