docker启动后Wifi连接断开

NaN*_*NaN 8 networking wifi docker

我通过Wifi登录到我的Lubuntu 16.04.2 LTS服务器,每次启动docker容器时,我的连接都会被丢弃.因为我对码头工具比较新,我只能猜测这与dockers虚拟网络创建有关.我还应该提到我禁用了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)
Run Code Online (Sandbox Code Playgroud)

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": {}
    }
]
Run Code Online (Sandbox Code Playgroud)

随着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
Run Code Online (Sandbox Code Playgroud)

我的Wifi连接会怎样?任何帮助表示赞赏.如果有更多信息有用,请告诉我.

UPDATE

谢谢你的帮助.根据我到目前为止的反应,我的网络配置似乎有些问题.

cat /etc/NetworkManager/NetworkManager.conf 节目

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

[ifupdown]
managed=false
Run Code Online (Sandbox Code Playgroud)

cat /etc/network/interfaces 节目

# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
Run Code Online (Sandbox Code Playgroud)

由于我没有特殊配置,一切看起来都很好.有什么建议,我可以寻找信息或如何解决问题?

UPDATE

nmcli dev 节目

DEVICE       TYPE      STATE        CONNECTION 
docker0      bridge    connected    docker0    
wlp2s0       wifi      unavailable  --         
vethf9342a9  ethernet  unmanaged    --         
lo           loopback  unmanaged    --  
Run Code Online (Sandbox Code Playgroud)

当docker正在运行时

DEVICE   TYPE      STATE      CONNECTION 
docker0  bridge    connected  docker0    
wlp2s0   wifi      connected  meins      
lo       loopback  unmanaged  --  
Run Code Online (Sandbox Code Playgroud)

当docker停止时.

UPDATE

添加以下行以/etc/NetworkManager/NetworkManager.conf使NetworkManager忽略docker接口.

[keyfile]
unmanaged-devices=interface-name:docker0;interface-name:veth*
Run Code Online (Sandbox Code Playgroud)

网络管理员忽略了接口,但问题仍然存在.所以我的猜测是,我的DHCP配置存在问题.

UPDATE

DHCP客户端似乎确实存在问题.禁用它有帮助.有关解决方法的任何建议吗?

Bel*_*ter 6

上同样的问题Ubuntu 18.04

我认为将以下内容添加到文件中/etc/NetworkManager/NetworkManager.conf已经解决了这个问题:

[keyfile]
unmanaged-devices=interface-name:docker0;interface-name:veth*
Run Code Online (Sandbox Code Playgroud)

你还需要做一些其他的事情:

  1. 停止所有的 docker 容器;
  2. 重启网络sudo service network-manager restart,现在你的wifi应该可以正常工作了;
  3. 再次启动您的 docker 容器,此时我的 wifi 仍在工作。

2019 年 3 月 14 日

参考:https : //askubuntu.com/a/1009402/620445


小智 0

我已经查看了您发布的系统日志,似乎存在一些身份验证问题:

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
Run Code Online (Sandbox Code Playgroud)

目前我只能说,请访问我在下面粘贴的链接:

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

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

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