** Description changed:
+ ========================
+ Impact: cannot lxc-execute in a container without private rootfs
+ Development fix: mount /proc when no rootfs is specified
+ Stable fix: same as development fix
+ Test case:
+ sudo lxc-execute --name test /bin/bash
+ Without the fix, this will fail. With the fix, it will
+ succeed.
+ Regression potential: This fix is cherrypicked from upstream, and
+ should not result in any regressions. The function
+ being modified is a crucial one though.
+ ========================
+
I get the following output when trying to start a container just running
bash as an app:
$ sudo lxc-execute --name test /bin/bash
lxc-execute: Permission denied - failed to change apparmor profile to
lxc-container-default
lxc-execute: invalid sequence number 1. expected 4
lxc-execute: failed to spawn 'test'
I'm attaching the contents of /var/log/lxc/test.log, which is the only log
file I can see.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: lxc 0.9.0-0ubuntu3.2
ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
Uname: Linux 3.8.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Fri Jun 7 08:09:18 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-04-27 (405 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
MarkForUpload: True
SourcePackage: lxc
UpgradeStatus: Upgraded to raring on 2013-04-26 (41 days ago)
lxcsyslog:
** Changed in: lxc (Ubuntu Raring)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1188501
Title:
lxc-execute fails to start container without rootfs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1188501/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
