So I inspected the container runtime, and it turns out to be that /etc/ssl/certs is a sym link to /etc/pki/tls/certs directory.
Modifiying the destinationDir caused the certificate to be injected, but the build process is still failing because the certificate is not in the global trusted CAs in the container.
Did anyone come across an issue like this where the outbound
internet connection going to an appliance that inspects the
traffic and injecting it's own certificate?
On 07/17/2018 08:50 AM, Ben Parees wrote:
-- Regards, Ahmed Ossama