fix-docker-networking-dns #23
Replies: 2 comments 2 replies
-
I spent the last 1.5 hours trying to learn docker and getting stuck on the first docker run command because of this issue. Your solution fixed it. How can I buy you a cup of coffee? Thank you. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Hi there @NotRobin! Thanks for the awesome blogpost. Unfortunately for me, the DNS doesn't seem to be the problem as your first smoke test immediately fails: # on vpn
$ docker run busybox ping -c 1 192.203.230.10
PING 192.203.230.10 (192.203.230.10): 56 data bytes
--- 192.203.230.10 ping statistics ---
1 packets transmitted, 0 packets received, 100% packet loss
# off vpn
$ docker run busybox ping -c 1 192.203.230.10
PING 192.203.230.10 (192.203.230.10): 56 data bytes
64 bytes from 192.203.230.10: seq=0 ttl=58 time=8.246 ms
--- 192.203.230.10 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 8.246/8.246/8.246 ms Could you recommend any other blog posts/guides/approaches? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
fix-docker-networking-dns
Within certain networks, docker is unable to resolve DNS correctly. When this happens, here's how to fix it.
https://robinwinslow.uk/fix-docker-networking-dns
Beta Was this translation helpful? Give feedback.
All reactions