Public bug reported:
I'n trying to get (unpriviliged) lxc containers to run on wily. I
create a container like this:
> lxc-create -t download -n u1 -- -d ubuntu -r wily -a amd64
that works. However, starting the container fails:
> lxc-start -n u1
Ah, right, that explains things: I'm running a xenial kernel, I think.
For completeness sake, these are the versions:
[bas@miranda]~> uname -a
Linux miranda 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
[bas@miranda]~> dpkg -l linux-image-\* systemd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Martin,
On 11-02-16 10:24, Martin Pitt wrote:
> Bas, any chance to test the update in -proposed so that we can
> release that?
I'll try to test it later this week, if that's ok.
Best regards,
Bas.
- --
And what shoulder and what art
Could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Martin,
> On 11-02-16 10:24, Martin Pitt wrote:
>> Bas, any chance to test the update in -proposed so that we can
>> release that?
>
> I'll try to test it later this week, if that's ok.
Unfortunately, the xenial 4.4 kernel won't boot for me
I've just tried with an upstream 4.5.0-rc4 kernel (which does boot on my
laptop).
Unfortunately, it doesn't work yet.
linux-image linux-image-4.5.0-040500rc4-generic
systemd 229-1ubuntu2
lxc 1.1.5-0ubuntu0.15.10.3
starting a container gives: lxc-start 1455712091.086 DEBUGlxc_console
This was systemd and kernel from xenial. I'll try again tomorrov with
the wily-proposed systemd and xenial kernel.
--
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/1533833
Title:
I've downgraded systemd to 225-1ubuntu9.1 from wily/proposed. Kernel is
still linux-image-4.5.0-040500rc4-generic and lxc is
1.1.5-0ubuntu0.15.10.3 from wily-updates.
Unfortunately, when I now start the lxc container, I seem to hit a
different bug. I get:
lxc-start 1455870309.289 INFO
strangely enough, adding the aa_allow_incomplete option doesn't seem to
make a difference; container startup keeps failing at the same point.
In any case, it does seem to initialize the container correctly, and I
seem to hit a different issue. The entire cgroup thing seems to work
now, at
