testcontainers / testcontainers/testcontainers-rs
Allow mapping container port to custom IPs in the host
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.1k
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Example:
# Cluster 0: 127.0.0.*
docker run --name cluster-0-n0 -d -p 127.0.0.1:6333:6333 qdrant/qdrant:latest
docker run --name cluster-0-n1 -d -p 127.0.0.2:6333:6333 qdrant/qdrant:latest
# Cluster 1: 127.0.1.*
docker run --name cluster-1-n0 -d -p 127.0.1.1:6333:6333 qdrant/qdrant:latest
docker run --name cluster-1-n1 -d -p 127.0.1.2:6333:6333 qdrant/qdrant:latest
This should be allowed by testcontainers-rs crate as well. I'm happy to create a PR for this if you agree. Thanks! :)
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 by tracing how the testcontainers-rs crate builds Docker port mappings and handles host bindings. Use the issue's custom-IP examples as the expected behavior, then add coverage for multiple host IPs and verify the resulting containers expose port 6333 on the requested addresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, rust
- Domain
- devops, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100