Link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ffĤ6: mtu 1500 qdisc noqueue master docker0 state UP group default Inet6 fe80::42:7fff:fe2d:f89c/64 scope linkĢ2: vboxnet0: mtu 1500 qdisc noop state DOWN group default qlen 1000 Link/ether 00:25:90:c5:53:61 brd ff:ff:ff:ff:ff:ffĤ: docker0: mtu 1500 qdisc noqueue state UP group default ID: 7MDY:2LCE:NMQ2:3INA:HL4A:LRTZ:VL43:TLBT:M5UN:PF7G:KKGN:AM6Dġ: lo: mtu 65536 qdisc noqueue state UNKNOWN group default Operating System: openSUSE Leap 42.1 (x86_64) Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Here are some relevant details I've seen other posts ask: linux-3nwo:/var/lib # docker infoĭata loop file: /var/lib/docker/devicemapper/devicemapper/data Why do I care when I can access the net using -net=host? Well, you can't build containers when the default networking doesn't work. Nothing so far has enabled my containers to connect to the net. I've disabled my firewall and flushed my iptables rules and followed many, many other suggestions in posts from many, many docker related issues that look like mine.
home/dnadave> docker run -it -rm debian:jessie ping 8.8.8.8Ĥ packets transmitted, 0 packets received, 100% packet loss home/dnadave> docker run -it -net=host -rm debian:jessie ping 8.8.8.8Ħ4 bytes from 8.8.8.8: icmp_seq=0 ttl=54 time=12.059 msĦ4 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=11.120 msĢ packets transmitted, 2 packets received, 0% packet loss The problem is that without specifying -net=host, I cannot access the internet from my docker containers. I'm on my second week of working through this problem and nothing on the internet has helped fix my issue.
0 kommentar(er)
