PIP_CERT / REQUESTS_CA_BUNDLE breaks TLS
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
Running on Docker In Docker and having to unset PIP_CERT and REQUESTS_CA_BUNDLE in order to connect to the docker service.
These env vars are set:
DOCKER_HOST: 'tcp://docker:2376'
DOCKER_TLS_CERTDIR: "/certs"
DOCKER_CERT_PATH: "$DOCKER_TLS_CERTDIR/client"
DOCKER_TLS_VERIFY: 1
It seems like they should take precedence over the above
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Docker-in-Docker setup using the listed DOCKER_* variables together with PIP_CERT and REQUESTS_CA_BUNDLE, then trace how TLS configuration is selected. Done means the Docker service connection works without unsetting those variables and the intended precedence is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100