Bug#865975: docker.io breaks (bridged) network for VMs

2017-07-31 Thread Roland Kammerer
Hi, docker is not configured in any special way, the only change to the config file was attached in the original report. Here are the relevant outputs of a full session after a fresh boot: after boot $ ip a s 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group

Bug#865975: docker.io breaks (bridged) network for VMs

2017-06-26 Thread Roland Kammerer
Package: docker.io Version: 1.13.1~ds1-2 Severity: critical Tags: upstream Justification: breaks unrelated software Dear Maintainer, * What led up to the situation? Any docker command like "docker images" * What was the outcome of this action? Network breaks for all libvirt VMs (i.e., they are

Bug#863248: containerd 0.2.3+git20170126.85.aa8187d~ds1-1: container not started (docker.io 1.13.0~ds1-3)

2017-05-24 Thread Roland Kammerer
Package: containerd Version: 0.2.3+git20170126.85.aa8187d~ds1-1 Severity: grave Justification: renders package unusable Dear Maintainer, I have the following versions: containerd: 0.2.3+git20170126.85.aa8187d~ds1-1 docker.io: 1.13.0~ds1-3 I report the bug against containerd because it shows up

Bug#855407: docker.io: Dependency missmatch (docker.io 1.11.2~ds1-6 vs. containerd 0.2.3~git20161117.78.03e5862~ds1-1)

2017-02-17 Thread Roland Kammerer
Package: docker.io Version: 1.11.2~ds1-6 Severity: grave Justification: renders package unusable Dear Maintainer, After the upgrade docker does not start anymore. Starting it manually produces the following output: sudo docker daemon --debug DEBU[] docker group found. gid: 125 DEBU[]