can't access docker's ports except using loopback address
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Using Photon OS 5.0 (OVA with virtual hardware v15)
the host can't access docker's ports.
Reproduction steps
example
docker run -p 1234:1234 alpine nc -l 1234
test 1: the host scan port on it's network address
nmap 192.168.1.xxx -p 1234
result port 1234 was filtered
test2: the host scan port on loopback address
nmap 127.0.0.1 -p 1234
result port 1234 was open
Expected behavior
expect ports opened on all network interfaces.
Additional context
No response
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 this on Photon OS 5.0 with docker run -p 1234:1234 alpine nc -l 1234, then compare the nmap results for the host network address and 127.0.0.1. Trace how Docker-published ports are exposed and identify why the port is filtered externally; done means the published port is reachable through the host's network address as well as loopback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100