the container create from replicas mode service can not resolve domain
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
If I create replicas mode service, the container created by the tasks can not resolve external domain . And can do in host.
core@worker-10-xx-x-34 ~ $ docker exec -it 0c0d7b939d11 sh
/ # ping mysql-gp-discuz-1-master
ping: bad address 'mysql-gp-discuz-1-master'
/ # exit
core@worker-10-xx-x-34 ~ $ docker version
Client:
Version: 1.12.1
API version: 1.24
Go version: go1.6.3
Git commit: 23cf638
Built: Thu Aug 18 17:52:38 2016
OS/Arch: linux/amd64
Server:
Version: 1.12.1
API version: 1.24
Go version: go1.6.3
Git commit: 23cf638
Built: Thu Aug 18 17:52:38 2016
OS/Arch: linux/amd64
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
No source file or test is named. Start by reproducing the replicas-mode service behavior with the documented Docker 1.12.1 setup, then trace the swarmkit networking and service-discovery entry points involved in task-container DNS. Done means the task containers can resolve the reported external domain and service name while the issue's host-side behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100