Just re-read through this whole bug.
It looks like what broke your setup is actually a bugfix in LXC wrt
config inheritance.
Your config contains:
- lxc.mount.auto =
- lxc.mount.auto = cgroup:mixed
This instructs LXC (and that wasn't implemented right at first) to wipe all of
lxc.mount.auto,
Hey Serge,
Thanks for looking into this more and better documentation would be most
helpful.
I'm not really sure if it matters any more, but my python script does
indeed ask to load /usr/share/lxc/config/ubuntu.common.conf. Here is
the code snippet before I start adding custom config options:
Quoting Christopher Townsend (christopher.towns...@canonical.com):
> 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 appa
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
Confused why this was marked confirmed/high prio, since there is as far
as I ca ntell no bug in lxc here.
The container rootfs came from an iso, but it's the configuration which
was bad. Wherever you got your configuration, fix it there to make sure
to mount a sysfs before attempting to mount thi
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
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
** Changed in: lxc (Ubuntu)
Status: Incomplete => 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 /
Hey Serge,
Yes, adding 'lxc.mount.auto = sys' fixes the issue.
The container is an extracted ISO from http://cdimage.ubuntu.com/ubuntu-
desktop-next/daily-live/current/vivid-desktop-amd64.iso for the Unity 8
in LXC project.
--
You received this bug notification because you are a member of Ubunt
thanks for submitting this bug. Could you tell us how you created the
container?
You should be able to solve this by adding
lxc.mount.auto = sys
as the first line of your configuration file. Please let us know if
that does not fix the container start.
** Changed in: lxc (Ubuntu)
Status
This is the debug output when starting the container.
** Attachment added: "debug.txt"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1417909/+attachment/4311947/+files/debug.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
This is the generated LXC config file.
** Attachment added: "config"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1417909/+attachment/4311948/+files/config
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubun
11 matches
Mail list logo