Where do Wired Networks come from?

Question

ubuntu

Good day, gentlemen.
I do not know what led to such a problem, but, it is the place to be. A set of "Wired network () Device not running" appears:

Network-manager restarted.
Any ideas why this might be?
Just in case: /etc/network/interface

auto lo
iface lo inet loopback

Constant reconnects, chrome, in general, goes crazy. Ubuntu 16.04
/var/log/syslog

Jun 25 11:59:08 Kovalchuk-main avahi-daemon[852]: Joining mDNS multicast group on interface veth377bce8.IPv6 with address fe80::a45b:b7f$
Jun 25 11:59:08 Kovalchuk-main avahi-daemon[852]: New relevant interface veth377bce8.IPv6 for mDNS.
Jun 25 11:59:08 Kovalchuk-main avahi-daemon[852]: Registering new address record for fe80::a45b:b7ff:fe5f:e66 on veth377bce8.*.
Jun 25 11:59:08 Kovalchuk-main avahi-daemon[852]: Joining mDNS multicast group on interface veth22fbf8a.IPv6 with address fe80::ec94:dff$
Jun 25 11:59:08 Kovalchuk-main avahi-daemon[852]: New relevant interface veth22fbf8a.IPv6 for mDNS.
Jun 25 11:59:08 Kovalchuk-main avahi-daemon[852]: Registering new address record for fe80::ec94:dfff:fed6:a74d on veth22fbf8a.*.
Jun 25 11:59:08 Kovalchuk-main avahi-daemon[852]: Interface veth6ead554.IPv6 no longer relevant for mDNS.
Jun 25 11:59:08 Kovalchuk-main avahi-daemon[852]: Leaving mDNS multicast group on interface veth6ead554.IPv6 with address fe80::78fd:38f$
Jun 25 11:59:08 Kovalchuk-main kernel: [  481.925259] br-1e8a1f9a705d: port 11(veth6ead554) entered disabled state
Jun 25 11:59:08 Kovalchuk-main kernel: [  481.928387] device veth6ead554 left promiscuous mode
Jun 25 11:59:08 Kovalchuk-main kernel: [  481.928393] br-1e8a1f9a705d: port 11(veth6ead554) entered disabled state
Jun 25 11:59:08 Kovalchuk-main avahi-daemon[852]: Withdrawing address record for fe80::78fd:38ff:fea6:fe3a on veth6ead554.
Jun 25 11:59:08 Kovalchuk-main NetworkManager[851]: <info>  [1498355948.4994] devices removed (path: /sys/devices/virtual/net/vethc70335$
Jun 25 11:59:08 Kovalchuk-main NetworkManager[851]: <info>  [1498355948.4996] devices removed (path: /sys/devices/virtual/net/veth6ead55$
Jun 25 11:59:08 Kovalchuk-main NetworkManager[851]: <info>  [1498355948.5007] device (vethc703358): driver 'veth' does not support carri$
Jun 25 11:59:08 Kovalchuk-main NetworkManager[851]: <info>  [1498355948.5011] device (veth6ead554): driver 'veth' does not support carri$
Jun 25 11:59:08 Kovalchuk-main NetworkManager[851]: <info>  [1498355948.6542] device (veth388ce9e): driver 'veth' does not support carri$
Jun 25 11:59:08 Kovalchuk-main kernel: [  482.109775] eth0: renamed from veth388ce9e
Jun 25 11:59:08 Kovalchuk-main NetworkManager[851]: <info>  [1498355948.6609] devices removed (path: /sys/devices/virtual/net/veth388ce9$

One of the iterations of complete nonsense.
dmesg -l warn:

[  691.824750] aufs au_opts_verify:1597:dockerd[6415]: dirperm1 breaks the protection by the permission bits on the lower branch

I started the docker, as I understand it, until it is started, these varnings are thrown out.
dmesg -l err is empty.
ifconfig:

br-1e8a1f9a705d Link encap:Ethernet  HWaddr 02:42:3c:83:04:52  
          inet addr:172.18.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
          inet6 addr: fe80::42:3cff:fe83:452/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1994 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:235652 (235.6 KB)

docker0   Link encap:Ethernet  HWaddr 02:42:01:55:03:cf  
          inet addr:172.17.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eno1      Link encap:Ethernet  HWaddr 2c:27:d7:da:d7:80  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Локальная петля (Loopback)  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:20318 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20318 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:2990210 (2.9 MB)  TX bytes:2990210 (2.9 MB)

veth2b373d0 Link encap:Ethernet  HWaddr b2:03:4f:2f:f1:de  
          inet6 addr: fe80::b003:4fff:fe2f:f1de/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2492 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:286266 (286.2 KB)

veth8ece6d2 Link encap:Ethernet  HWaddr 6a:20:9d:7c:21:18  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlp2s0b1  Link encap:Ethernet  HWaddr cc:52:af:94:5e:2b  
          inet addr:192.168.0.102  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::b94:c4:c4f:3d7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:49299 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36462 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:37736518 (37.7 MB)  TX bytes:5431067 (5.4 MB)

Answer 1

Too little data.
Show what at least ifconfig and mii-tool write.

Answer 2

Start with
dmesg -l err and dmesg -l warn
Read
/var/log/syslog