docker should not de-configure pre-existing bridge interfaces
Bug #1647376 reported by
Stefan Bader
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
docker.io (Ubuntu) |
Fix Released
|
High
|
Michael Hudson-Doyle | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[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:/
[Regression potential]
See above.
tags: | added: patch |
Changed in docker.io (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in docker.io (Ubuntu Yakkety): | |
status: | New → In Progress |
description: | updated |
tags: |
added: verification-done-xenial verification-done-yakkety removed: verification-done |
To post a comment you must log in.
This would be the proposed update for Zesty (the version this is based on is currently in proposed).