Docker启动后Wifi连接丢失

我通过Wifilogin到我的Lubuntu 16.04.2 LTS服务器,每次启动Docker容器时,连接都会断开。 因为我对docker工人来说比较陌生,所以我只能猜测这与docker工人的虚拟networking创build有关。 我还应该提到,我禁用了ipv6,但是如果启用它没有任何区别。

这里是我的系统日志 ,它显示了当我运行sudo docker run -it ubuntu bash时会发生什么情况。 我可以看到容器/ Ubuntu的提示2-3秒,然后冻结。 运行它--net=host工作,但不是我想要的。

ifconfig显示

 docker0 Link encap:Ethernet HWaddr 02:42:8d:8b:b7:4c inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:162 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:536 (536.0 B) TX bytes:9678 (9.6 KB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:538 errors:0 dropped:0 overruns:0 frame:0 TX packets:538 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:49592 (49.5 KB) TX bytes:49592 (49.5 KB) vethee1cf14 Link encap:Ethernet HWaddr ba:53:4c:08:89:64 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:167 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:648 (648.0 B) TX bytes:9888 (9.8 KB) wlp2s0 Link encap:Ethernet HWaddr f4:06:69:5d:ba:f6 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:3082 errors:0 dropped:0 overruns:0 frame:0 TX packets:2916 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:556197 (556.1 KB) TX bytes:569381 (569.3 KB) 

docker network inspect bridge表演

 [ { "Name": "bridge", "Id": "8ec46d17f5cba798c8aba5c8457e019dcb24eade1285054f59c3430c33ff74f8", "Created": "2017-03-04T10:44:27.966018717+01:00", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "172.17.0.0/16", "Gateway": "172.17.0.1" } ] }, "Internal": false, "Attachable": false, "Containers": {}, "Options": { "com.docker.network.bridge.default_bridge": "true", "com.docker.network.bridge.enable_icc": "true", "com.docker.network.bridge.enable_ip_masquerade": "true", "com.docker.network.bridge.host_binding_ipv4": "0.0.0.0", "com.docker.network.bridge.name": "docker0", "com.docker.network.driver.mtu": "1500" }, "Labels": {} } ] 

docker工人停止ip a节目

 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether f4:06:69:5d:ba:f6 brd ff:ff:ff:ff:ff:ff inet 192.168.178.21/24 brd 192.168.178.255 scope global wlp2s0 valid_lft forever preferred_lft forever inet6 fe80::f606:69ff:fe5d:baf6/64 scope link valid_lft forever preferred_lft forever 3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:6f:0c:38:7a brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 scope global docker0 valid_lft forever preferred_lft forever 

我的Wifi连接会发生什么? 任何帮助表示赞赏。 如果更多的信息会有所帮助,请让我知道。

UPDATE

Thx为你提供帮助。 根据我到目前为止的答复,我的networkingconfiguration似乎有问题。

cat /etc/NetworkManager/NetworkManager.conf显示

 [main] plugins=ifupdown,keyfile,ofono dns=dnsmasq [ifupdown] managed=false 

cat /etc/network/interfaces显示

 # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback 

由于我没有特别的configuration,一切看起来都很好。 任何build议,我可以寻找信息或如何解决这个问题?

UPDATE

nmcli dev显示

 DEVICE TYPE STATE CONNECTION docker0 bridge connected docker0 wlp2s0 wifi unavailable -- vethf9342a9 ethernet unmanaged -- lo loopback unmanaged -- 

而docker正在运行和

 DEVICE TYPE STATE CONNECTION docker0 bridge connected docker0 wlp2s0 wifi connected meins lo loopback unmanaged -- 

docker停止时。

UPDATE

/etc/NetworkManager/NetworkManager.conf添加了以下内容,以使NetworkManager忽略/etc/NetworkManager/NetworkManager.conf接口。

 [keyfile] unmanaged-devices=interface-name:docker0;interface-name:veth* 

networkingpipe理员忽略了接口,但问题依然存在。 所以我的猜测是,这是我的DHCPconfiguration问题。

从你的日志中突出的线条是:

 Mar 1 13:54:44 kodi NetworkManager[1054]: <info> [1488372884.3614] device (docker0): link connected Mar 1 13:54:44 kodi dhcpcd[1240]: veth48067d8: IAID 3a:d3:8a:28 Mar 1 13:54:44 kodi dhcpcd[1240]: veth48067d8: using static address 192.168.178.21/24 Mar 1 13:54:44 kodi dhcpcd[1240]: wlp2s0: preferring 192.168.178.21 on veth48067d8 Mar 1 13:54:44 kodi dhcpcd[1240]: veth48067d8: adding route to 192.168.178.0/24 Mar 1 13:54:44 kodi dhcpcd[1240]: veth48067d8: adding default route via 192.168.178.1 

在我自己的环境中,在NetworkManager看到连接的链接后,我只能看到以下内容:

 Mar 5 12:32:39 bmitch-asusr556l NetworkManager[827]: <info> devices removed (path: /sys/devices/virtual/net/veth365c591, iface: veth365c591) Mar 5 12:32:39 bmitch-asusr556l NetworkManager[827]: <info> (vethf29a6bb): link connected Mar 5 12:32:41 bmitch-asusr556l avahi-daemon[835]: Joining mDNS multicast group on interface vethf29a6bb.IPv6 with address fe80::34c0:66ff:fe89:26ec. Mar 5 12:32:41 bmitch-asusr556l avahi-daemon[835]: New relevant interface vethf29a6bb.IPv6 for mDNS. Mar 5 12:32:41 bmitch-asusr556l avahi-daemon[835]: Registering new address record for fe80::34c0:66ff:fe89:26ec on vethf29a6bb.*. 

我在上面的评论中的问题,在哪里弄清楚,如果你有不知何故硬编码您的容器IP到192.168.178.xnetworking。 由于没有发生,您应该看到容器以172.17.0.x的地址旋转起来。 在您的环境中似乎有一个NetworkManager或dhcpd的configuration错误,正在尝试使用您的无线(wlp2s0)使用的相同IP为docker容器(veth)提供一个IP,然后该容器被列为首选连接。

我已经通过你发布的系统日志,似乎有一些身份validation问题:

 Mar 1 13:54:45 kodi kernel: [351489.718503] wlp2s0: deauthenticating from 34:31:c4:0c:bf:24 by local choice (Reason: 3=DEAUTH_LEAVING) Mar 1 13:54:45 kodi dhcpcd[1240]: veth48067d8: carrier acquired Mar 1 13:54:45 kodi wpa_supplicant[1259]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=34:31:c4:0c:bf:24 reason=3 locally_generated=1 Mar 1 13:54:45 kodi NetworkManager[1054]: <warn> [1488372885.1783] sup-iface[0x23b4210,wlp2s0]: connection disconnected (reason -3) Mar 1 13:54:45 kodi kernel: [351489.751908] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready 

暂时我只能说,请通过我粘贴下面的链接:

https://docs.docker.com/engine/admin/#logs-1

http://www.tutorialspoint.com/articles/how-to-install-and-use-docker-on-ubuntu-16-04

如果这不能解决您的问题,请按照以下debugging步骤发布更合适的日志。