group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1647376@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package docker.io - 1.12.3-0ubuntu4

---------------
docker.io (1.12.3-0ubuntu4) zesty; urgency=medium

  * Explicity depend on the version of runc that was built with seccomp
    support.

 -- Michael Hudson-Doyle <michael.hudson@xxxxxxxxxx>  Mon, 12 Dec 2016
11:15:01 +1300

** Changed in: docker.io (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1647376

Title:
  docker should not de-configure pre-existing bridge interfaces

Status in docker.io package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  New
Status in docker.io source package in Yakkety:
  New

Bug description:
  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).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1647376/+subscriptions