Skip to content

[Docker] Custom CA Certificate configuration for GitHub Enterprise usage #369

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rkargMsft opened this issue May 3, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@rkargMsft
Copy link

Describe the feature or problem you’d like to solve

GitHub Enterprise instances can utilize internal CA certificates and the docker container doesn't have a defined way to provide custom CA certs.

Proposed solution

Document (and implement if necessary) a preferred way to provide custom CA certificates for working with GitHub Enterprise instances.

Additional context

The Docker image is based on a distroless image so there isn't a straight forward way to do this right now.

@rkargMsft rkargMsft added the enhancement New feature or request label May 3, 2025
@williammartin
Copy link
Collaborator

Not being familiar with this feature, is this the GitHub doc describing it: https://docs.github.com/en/enterprise-server@3.16/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-tls?

@rkargMsft
Copy link
Author

The issue is that when the MCP server is running in the docker container, it makes https connections to the GitHub server. In our case, that's a GitHub Enterprise instance that uses a TLS certificate that's signed by our internal Certificate Authority (CA). But that internal CA is not a publicly trusted CA that is built in to operating systems so it needs to be installed/trusted inside the container.

This is normally done by either building a new container based on the base container or by updating the CMD to run the container to copy in the CA and update-cacertificates, but the distroless container doesn't have that tooling installed so it's not immediately clear how that's expected to be achieved.

Also, it would be better to have a built in way to add trusted CA certificates as I would imagine many GitHub Enterprise setups use internal CAs and it would be wasteful to have each of them set up their own build process to create new container images with their custom CAs installed in them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants