Error upon cloning repository due to CA Cert

[elronzo]

In our corporate environment we do have a WebProxy that breaks up SSL connections. As a consequence clients need to trust that proxy's Certificate or its internal issuing CA.

How could I let devpod know about the proxy's cert and/or its CA?

[bkneis]

Hi @elronzo thanks for providing some details about your use case. Can you tell me more about what is currently not working? If you could add --debug to your command and send the logs that would be ideal.

On first thought I suspect you will need to add your CA to your system's root trust, so devpod can verify the proxy's connection

[elronzo]

I will provide more info ASAP.

I saw that loftlabs is attending OpenSourceSummit Europe. Maybe we'll find some time to discuss remaining issues...

[kalebharrison]

I am also running into this same issue.

The devpod container itself pulls down fine since the host itself has the certificate trusted, but when the devpod container attempts to connect to the repo, it fails because the devpod container does not have the certificate in its truststore.

This can be tested by using self-signed certificates.

I think the question is how do we inject certificates into the truststore of the devpod container before it attempts to clone/pull anything external.

[bkneis]

@kalebharrison you could mount the certificates into the trust store?

[github-actions[bot]]

This issue is stale because it has been open for 60 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 30 days since being marked as stale.