** Also affects: lxc (Ubuntu Precise)
Importance: Undecided
Status: New
** Description changed:
+ ======================================
+ SRU Justification:
+ Impact: application containers cannot be used without rootfs
+ Stable fix: will be same as development fix
+ Development fix: don't try to pin rootfs is rootfs is null, and don't try
+ to mount /proc if rootfs is null.
+ Test case:
+ cat > lxc.conf << EOF
+ lxc.aa_profile = unconfined
+ EOF
+ lxc-execute -n test -f lxc.conf /bin/bash
+ Regression potential: In normal containers, rootfs is not null, so these paths
+ should not be affected
+ ======================================
+
per http://www.techrepublic.com/blog/opensource/introducing-linux-
virtual-containers-with-lxc/1289
a minimal trival lxc should be doable as
lxc-execute -n test /bin/bash
but on my precise laptop this results in:
sudo lxc-execute -n test /bin/bash
lxc-execute: Invalid argument - failed to get real path for '(null)'
lxc-execute: failed to pin the container's rootfs
lxc-execute: failed to spawn 'test'
lxc-execute: No such file or directory - failed to remove cgroup
'/sys/fs/cgroup/cpuset//lxc/test'
--
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/981955
Title:
lxc-execute without config does not seem to work in precise
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/981955/+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
