Following up this post, I am giving out the solution to the problem.
Please revise the alipapa.yml, on the network part
networks:
papa.com:
driver: bridge
If I want to give a name to the network bridge, can I do thing like this?
networks:
papa.com:
driver: bridge
name: papa.com
Let's try out, and docker-compose it up!
ubuntu@ip-172-31-11-243:~$ docker-compose -f alipapa.yml up -d
Creating network "papa.com" with driver "bridge"
Recreating ali01 ... done
Recreating ali02 ... done
I can sense the smell of success. But, let's find out more.
ubuntu@ip-172-31-11-243:~$ docker exec -ti ali01 bash
root@ali01:/# hostname -f
ali01.papa.com
root@ali01:/# ping ali01
PING ali01.papa.com (172.18.0.2) 56(84) bytes of data.
64 bytes from ali01.papa.com (172.18.0.2): icmp_seq=1 ttl=64 time=0.036 ms
64 bytes from ali01.papa.com (172.18.0.2): icmp_seq=2 ttl=64 time=0.034 ms
root@ali01:/# ping ali02
PING ali02 (172.18.0.3) 56(84) bytes of data.
64 bytes from ali02.papa.com (172.18.0.3): icmp_seq=1 ttl=64 time=0.076 ms
64 bytes from ali02.papa.com (172.18.0.3): icmp_seq=2 ttl=64 time=0.066 ms
64 bytes from ali02.papa.com (172.18.0.3): icmp_seq=3 ttl=64 time=0.065 ms
ubuntu@ip-172-31-11-243:~$ docker network ls
NETWORK ID NAME DRIVER SCOPE
8e0851dec6fd papa.com bridge local
07cb97e27689 bridge bridge local
e81946364c3d host host local
b285c6c7236e none null local
5fb1bdc9f13e ubuntu_papa.com bridge local
Indeed! Problem has been solved. ali01.papa.com and ali02.papa.com is returning nicely to me as well. Thank you so much for the docker embedded DNS engine! The DNS resolution is working out of the box!
No comments:
Post a Comment