Open ajyounge opened 3 years ago
I can't reproduce this. I'm sure it depends on the details of your proxy setup. Can you point us to documentation on that?
Documentation on the proxy is basically in the example envars listed above, just with local URLs. There are also root certificates on the host machine that enable valid SSL/TLS traffic from the corporate network. I can share more details if you have access to Sandia's corporate network. While certainly annoying, this setup is fairly common for many enterprise networks.
Given the error from Charliecloud, I'm not sure which one (or both?) is causing the issue; proxy or certificates. I can only assume CH can be configured to pick up proxy and use the system certs like any normal process? However I am not aware of any way beyond standard system envars to configure Charliecloud.
Does ch-image --tls-no-verify build -f Dockerfile.centos7 .
work? This will turn off TLS certificate verification.
I was able to reproduce this. Configuring the host system to trust the proxy’s root cert fixed the pull itself.
However, the image also needs to be configured to trust the relevant certificates if it does any TLS stuff.
Using Charlielcoud from master (0.23~pre+4715a0f), ch-image fails to properly pull an image on a system. Suspect problem is with Charliecloud not able to use basic PROXY setup and the corporate SSL certificate installe don host. I cannot pull a basic image from likely any external registry due to this bug. Tested on aarch64 but suspect problem with Charliecloud is independent of uarch.
Also tested against rootless Podman using the same Dockerfile, which properly detects and uses the system proxy settings and works as expected, verifying the Dockerifle.