Quoting David Favor (da...@davidfavor.com): > Correct. It appears the default template processing (default meaning no > template specified) seems like it could use a bit of work.
Ok, thanks. > Seems like specifying no template should either throw an error or create > some form of container that will start. For anyone reading this report who may not be clear on it, the current behavior is: a template exists to fill in a rootfs. If no template is specified, then it is assumed that a rootfs has already been created, and only the basic metadata (rootfs location etc) are to be filled in. People do rely on this behavior. So the question is how to best avoid the (more common imo) case where a user accidentally does not specify a template. We could force the existing no-template users to switch to specifying '-t none'. We could simply document the current behavior. We could print out a warning about there being no template, but not change the default behavior. Not sure if there are any other ideas. So the question is how to best handle this without causing trouble for people who rely on this default behavior. subject: change default template handling status: triaged importance: wishlist ** Changed in: libcgroup (Ubuntu) Importance: Undecided => Wishlist ** Changed in: libcgroup (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271000 Title: lxc-start fails with Out of memory reading cgroups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs