← Back to team overview

touch-packages team mailing list archive

Re: [Bug 1417909] Re: Container fails to start with error mounting /sys/fs/cgroup

 

Quoting Christopher Townsend (christopher.townsend@xxxxxxxxxxxxx):
> 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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1417909

Title:
  Container fails to start with error mounting /sys/fs/cgroup

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  It seems a fairly recent update to LXC has caused this.  This is a
  privileged container.  I will attach debug output when trying to start
  the container.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.0~rc4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb  4 02:41:39 2015
  InstallationDate: Installed on 2013-03-18 (687 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: lxc
  UpgradeStatus: Upgraded to vivid on 2014-10-20 (106 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1417909/+subscriptions


References