From 17f95863e49fd59741224e8ef786aa702834a725 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 13 Mar 2016 10:00:40 +0100 Subject: Adding documentation about current bugs (FIXME). --- share/doc/BUGS.txt | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 share/doc/BUGS.txt diff --git a/share/doc/BUGS.txt b/share/doc/BUGS.txt new file mode 100644 index 0000000..897e00f --- /dev/null +++ b/share/doc/BUGS.txt @@ -0,0 +1,37 @@ +container-tools: Bugs +===================== + + +1. veth not removed on container stop +------------------------------------- + +When stopping a container, it irregularly but reproducibly happen that the +corresponding veth device of the container is not shutdown, making it +impossible to start the container again. + +This is caused by a kernel bug not cleaning up veth devices on container +collapsing. The veth device is supposed to be go away automatically after +some time, definitely after a reboot though. + +A manual workaround is to shutdown the veth device manually with: + +# ip link delete ${VETH_DEVICE} + +There is a patch for it, see for more information: +http://lists.linuxfoundation.org/pipermail/containers/2012-October/030533.html + +FIXME: add nspan message about it here + +2. bug with machine.slices etc +------------------------------ + +FIXME + +3. veth length +-------------- + +systemd creates veth devices on the fly and names them vb-$NAME, where NAME is the +container name truncated to the first 10 characters. + +Problem: if you have several containers named with the first 10 characters to be +identical, systemd will not be able to create a new veth device. -- cgit v1.2.3