Bug 787487 - Please add "docker[0-9]*" to 85-nm-unmanaged.rules
Please add "docker[0-9]*" to 85-nm-unmanaged.rules
Status: NEW
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2017-09-09 20:44 UTC by Julian Andres Klode
Modified: 2017-09-10 10:59 UTC (History)
1 user (show)

See Also:
GNOME target: ---
GNOME version: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Julian Andres Klode 2017-09-09 20:44:23 UTC 
Docker provides bridges like docker0 which are managed by itself, they should not be managed by network-manager, so please add

ENV{INTERFACE}=="docker[0-9]*", ENV{NM_UNMANAGED}="1" 

Thanks.
Comment 1 Thomas Haller 2017-09-10 10:50:42 UTC 
especially for software devices that are not created by NM, NM should not interfere without marking them unmanaged.

What issue to you have?
Comment 2 Julian Andres Klode 2017-09-10 10:59:02 UTC 
My main issue is that if they are treated as managed, nm-online thinks the system is online all the time, even if no actual network connection exists.

And well, I can manipulate if from nmcli and am led to believe that NM is managing the connection, because well, that's what nmcli tells me, so I'll try to turn it off with nmcli and other stuff.
Note You need to log in before you can comment on or make changes to this bug.