Harbor can't access registry-1.docker.io in Photon 3.0
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
Harbor which is a popular container registry, after installed on Photon 3.0, it can't access any internet website, while it's good in Photon 2.0 or other OS.
Please help check what change in Photon 3.0 make this broken.
Relative issue https://github.com/goharbor/harbor/issues/9218.
Reproduce step:
- install docker
- docker run --rm -it --dns-search . busybox ping www.baidu.com
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 with the Photon 3.0 environment and reproduce the reported command: docker run --rm -it --dns-search . busybox ping www.baidu.com. Compare its network and DNS behavior with Photon 2.0, and read the linked Harbor issue for related findings. Done means identifying the Photon 3.0 regression and documenting or fixing it so the container can reach registry-1.docker.io.
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
- Mostly clear
- Newbie friendliness
- 35/100