Thanks for reporting this bug. Your example pointed me to the root of the problem, which has been around for awhile.
This patch, plus upstream commit fabf7361da4845cd6cf268e0e85c3c6a1c0b0be4 (from this morning), fixes the bug for me. ** Patch added: "0001-conf.c-if-we-don-t-specify-a-rootfs-we-still-need-pr.patch" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1188501/+attachment/3699842/+files/0001-conf.c-if-we-don-t-specify-a-rootfs-we-still-need-pr.patch ** Changed in: lxc (Ubuntu) Status: Confirmed => In Progress ** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Serge Hallyn (serge-hallyn) -- 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/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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
