This bug was fixed in the package systemd - 225-1ubuntu9.1
---
systemd (225-1ubuntu9.1) wily-proposed; urgency=medium
* Add "pids" cgroup controller to user LXC support patch. Fixes running with
newer kernels. (LP: #1533833)
-- Martin Pitt Mon, 18 Jan 2016 21:54:41
+0100
**
Marking verification-done bc the pids cgroup problem is addressed. If
you continue to have a problem with the apparmor profile, please file a
new bug.
** Tags removed: verification-failed verification-needed
** Tags added: verification-done
--
You received this bug notification because you are
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 least:
Quoting Bas Zoetekouw (b...@debian.org):
> 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
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
Thanks - do make sure to log back in after the update.
The xenial systemd would fail because there you must have libpam-cgfs
to get your own cgroups for lxc. In wily iirc that should not be
required.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
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:
unprivi
Oh, right, something with the pids controller enabled.
Still want to make sure he's using the right systemd version, since his
appears not to be fixed otherwise.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bu
Serge Hallyn [2016-02-18 16:39 -]:
> Just to be sure, can you show the systemd version you were using here?
> The intent was to check with systemd from wily-proposed, with the
> regular wily kernel.
I thought the idea was to use a xenial kernel on wily?
--
You received this bug notification
Just to be sure, can you show the systemd version you were using here?
The intent was to check with systemd from wily-proposed, with the
regular wily kernel. In particular, an upstream kernel would be
expected to fail by default without setting an extra apparmor flag in
the container configuration
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
-
-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 at
-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
bug 1539488 is nothing new and not related to systemd.
** Tags removed: verification-failed
--
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:
unprivileged lxc containers wo
Bas, any chance to test the update in -proposed so that we can release
that?
--
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:
unprivileged lxc containers won't start, need
Bug 1538960 is unrelated and a local configuration error.
** Tags removed: verification-failed
--
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:
unprivileged lxc containers
Hello Bas, or anyone else affected,
Accepted systemd into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/225-1ubuntu9.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
Tested it myself now as well. I uploaded it to the wily-proposed SRU
queue.
--
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:
unprivileged lxc containers won't start, need t
Thanks - Martin - tested that with the mainline kernel, and it did indeed
give me a pids cgroup:
ubuntu@pitti:~$ cat /proc/self/cgroup
11:hugetlb:/user.slice/user-1000.slice/session-2.scope
10:blkio:/user.slice/user-1000.slice/session-2.scope
9:devices:/user.slice/user-1000.slice/session-2.scope
8
I uploaded a systemd with adding the "pids" cgroup controller to
https://launchpad.net/~pitti/+archive/ubuntu/ppa . It would be great if
you could test this! (Sorry, running out of time today.)
** Changed in: systemd (Ubuntu Wily)
Status: Triaged => In Progress
** Changed in: systemd (Ubun
20 matches
Mail list logo