testcontainers / testcontainers/testcontainers-python
Feature: ryuk should be able to use TCP socket to connect to Docker engine API
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 386
- Avg merge
- 4h 40m
- Merged PRs (30d)
- 1
Description
What are you trying to do?
I'm trying to run testcontainers on a host with Docker Engine API exposed via TCP socket instead of a Unix socket. Testcontainers run fine but ryuk fails to start because it wants to bind mount /var/run/docker.sock into container.
Using unix socket and bind mounts is hardcoded here:
Supporting mTLS TCP sockets would also be cool. mTLS support may be split off into another issue though.
Other references:
- Similar issue in testcontainers-java: https://github.com/testcontainers/testcontainers-java/issues/9137
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
Start in core/testcontainers/core/container.py at lines 285-293, where the Unix socket and bind mount are hardcoded, and trace how Ryuk receives its Docker connection. Define how a TCP socket should be configured and used instead; supporting mTLS can remain separate. Done means Ryuk can connect when Docker Engine is exposed through TCP rather than only /var/run/docker.sock.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100