testcontainers / testcontainers/testcontainers-java
ContainerInfo Port bindings are NULL when upgrading to 1.16.0
Open
Nobody has claimed this yet.
resolution/waiting-for-info
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
container.getContainerInfo().getNetworkSettings().getPorts().getBindings()
with 1.15.3 returns
"8080/tcp" -> [ "0.0.0.0:49302", ":::49302" ]
with 1.16.0 returns
"8080/tcp" -> null
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 reproducing the reported difference through container.getContainerInfo().getNetworkSettings().getPorts().getBindings() on versions 1.15.3 and 1.16.0. Trace the ContainerInfo network-settings path and compare the returned port-binding data; done means the 1.16.0 behavior no longer returns null for the reported 8080/tcp binding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- infrastructure, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100