*** This bug is a duplicate of bug 1325468 ***
https://bugs.launchpad.net/bugs/1325468
I reproduced the situation: Reverted the apparmor profile to what's in
utopic, booted with systemd, ran "sudo ./lxc-net start", and tried to
start my "debci" container (unconfined apparmor, Ubuntu trusty).
This leaks the following mounts:
/home/martin/.Private on /usr/lib/x86_64-linux-gnu/lxc/home/ubuntu/debci type
ecryptfs
(rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=a44ae562e9394275,ecryptfs_sig=e4e769aed2e4cb79,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
devpts on /scratch/lxc/debci/rootfs/dev/lxc/console type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /scratch/lxc/debci/rootfs/dev/lxc/tty1 type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/tty1 type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /scratch/lxc/debci/rootfs/dev/lxc/tty2 type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/tty2 type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /scratch/lxc/debci/rootfs/dev/lxc/tty3 type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/tty3 type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /scratch/lxc/debci/rootfs/dev/lxc/tty4 type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/tty4 type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
As /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console is a mount point, that
explains the EIO when trying to creat() it.
As this is a direct result from a failure to remount the container fs as
a slave, I think there is not much point in trying to clean this up, and
we should just fix the apparmor profile (bug 1325468). Hence I close
this now.
** This bug has been marked a duplicate of bug 1325468
[systemd] container startup fails with AppArmor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325470
Title:
[systemd] error 5 creating /usr/lib/x86_64-linux-
gnu/lxc/dev/lxc/console after failed container startup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1325470/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
