** Description changed: - Since moving to docker 1.12, management of networks to be used by docker - images is done via "docker network (create/rm)". Currently docker - assumes (for the bridge driver at least) that it has to do full - setup/cleanup of the associated bridge interface. This is fatal for - those cases where an existing bridge interface is used to declare the - network to docker. + [Impact] + Since moving to docker 1.12, management of networks to be used by docker images is done via "docker network (create/rm)". Currently docker assumes (for the bridge driver at least) that it has to do full setup/cleanup of the associated bridge interface. This is fatal for those cases where an existing bridge interface is used to declare the network to docker. This is fixed in docker 1.13 by the attached patch (this is a backport from docker upstream, it applies to yakkety and xenial but has to drop one more hunk in zesty). + + [Test Case] + See https://wiki.ubuntu.com/DockerUpdates + + [Regression potential] + See above.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647376 Title: docker should not de-configure pre-existing bridge interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1647376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
