[Bug 1325470] Re: [systemd] error 5 creating /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console after failed container startup

[Martin Pitt]

*** This bug is a duplicate of bug 1350947 ***
https://bugs.launchpad.net/bugs/1350947

** This bug is no longer a duplicate of bug 1325468
   [systemd] container startup fails with AppArmor
** This bug has been marked a duplicate of bug 1350947
   apparmor: no working rule to allow making a mount private

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in 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-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1325470] Re: [systemd] error 5 creating /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console

[Martin Pitt]

Ah, turns out this is just fallout from bug 1325468. Apparently that
failed startup left the /usr/lib/x86_64-linux-gnu/lxc/dev/ directory on
my host system, which then causes this error. After a reboot the
directory is gone and (unconfined) container startup works.

** Changed in: lxc (Ubuntu)
   Importance: Undecided = Wishlist

** Changed in: lxc (Ubuntu)
   Importance: Wishlist = Low

** Summary changed:

- [systemd] error 5 creating /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console
+ [systemd] error 5 creating /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console 
after failed container startup

** Tags removed: systemd-boot

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in 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-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1325470] Re: [systemd] error 5 creating /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console after failed container startup

[Martin Pitt]

*** 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
Server Team, which is subscribed to lxc in 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-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs