https://bugzilla.redhat.com/show_bug.cgi?id=1075232
Bug ID: 1075232 Summary: 0.9.0 Adds virtual interface, NetworkManager attempts to assign dhcp address to it Product: Fedora Version: 20 Component: docker-io Assignee: lsm5@redhat.com Reporter: admiller@redhat.com QA Contact: extras-qa@fedoraproject.org CC: admiller@redhat.com, golang@lists.fedoraproject.org, lsm5@redhat.com, mattdm@redhat.com, mgoldman@redhat.com, skottler@redhat.com, vbatts@redhat.com
Created attachment 873221 --> https://bugzilla.redhat.com/attachment.cgi?id=873221&action=edit snippet from /var/log/messages for my laptop around the virtual interface events
Description of problem: When you install docker-io-0.9.0 on Fedora 20, it creates a new virtual interface
13: vethf3e3: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master docker0 state UP group default qlen 1000 link/ether 1a:9c:40:61:1e:8b brd ff:ff:ff:ff:ff:ff inet6 fe80::189c:40ff:fe61:1e8b/64 scope link valid_lft forever preferred_lft forever
Something (I'm thinking dbus or udev) causes NetworkManager to launch dhclient for the new interface, and if you're running with a Desktop Environment this causes a visual change to the NM applet which can be confusing. It doesn't ever do anything, NM eventually times out and gives up and this doesn't appear to impact docker's functionality at all (or at least not yet in my tests have I found an issue, networking works fine).
Version-Release number of selected component (if applicable): docker-io-0.9.0-2.fc20.x86_64
How reproducible: Always
Steps to Reproduce: 1. yum install docker-io #on a machine with a GUI/DE up and running with NetworkManager
Actual results: NetworkManager attempts to get a dhcp lease on the new virtual interface.
Expected results: NetworkManager probably shouldn't attempt to get a dhcp lease on the new virtual interface, this seems odd.
Additional info: