Quoting Christopher Townsend ([email protected]):
> Hi Serge,
>
> Ok, I understand I can fix this issue by adding that line in my config.
>
> However, my gripe now with this is that my configuration was working
> with no issues prior to an update in LXC, then it broke for no apparent
> reason. Why was it automounting /sys before and not now? Shouldn't
> this be a default when pulling in
> /usr/share/lxc/config/ubuntu.common.conf as I do in my config?
Your config includes /usr/share/lxc/config/common.conf, not
/usr/share/lxc/config/ubuntu.common.conf .
If you created a configuration using 'lxc-create', and that turned
out not forward-compatible, then I would consider that a bug. And
given the churn there has been recently I wouldn't be surprised if
there were such cases. However, if your config was hand-created,
then while I still consider this unfortunate, the newly increased
commonality between config layouts for different distributions is
worthwhile.
I wonder whether we can come up with a versioning/backup scheme for
configuration files to prevent this sort of thing in the future.
The trick is that for most containers we do want to take updated
configuration files, as that's the whole point.
Perhaps what we need, the real bug here, is better documentation
of what the *.$distro.* and *.common.* really mean and what a user
is safe to use.
status: confirmed
importance: medium
** Changed in: lxc (Ubuntu)
Importance: High => Medium
** Changed in: lxc (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1417909
Title:
Container fails to start with error mounting /sys/fs/cgroup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1417909/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
