This bug was fixed in the package systemd - 217-2ubuntu1
---
systemd (217-2ubuntu1) vivid; urgency=medium
* Merge with Debian unstable. See 217-1ubuntu1 for remaining Ubuntu changes.
* Put session scopes into all cgroup controllers instead of their parent
user slices. This wor
Finally!
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu&id=1e76bb017a447d92b224f0476d5d5551bbd16850
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
The above patches are included in
https://launchpad.net/ubuntu/+source/systemd/215-6ubuntu2, but they
still don't work quite right: They seem to work well through VT logins
and ssh, but not through lightdm. There's some race condition somewhere
which removes PIDs from the session cgroup controllers
Got it working now, with the patch set on
http://people.canonical.com/~pitti/tmp/systemd-unpriv-lxc/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1346734
Title:
Unprivil
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1346734
Title:
Unprivileged LXC containers don't work
Ah, nevermind; it wanted to write
/sys/fs/cgroup/cpuset//cgroup.clone_children, which is probably an
artifact of cpuset not being included in the "join all controllers"
bits.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sys
I created a per-user container "t1", and confirm that it does start
under upstart/cgmanger and doesn't under systemd. I now have a
preliminary patch for putting the user slices into all cgroup
controllers, plus some hand-crafted "chown ubuntu" for all the
user-1000.slice cgroup directories so that
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-14.12
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:/
For my own notes: No hints from upstream; my current theory is that the
best place to hook this in would be in src/core/service.c
service_spawn(): After a successful exec_spawn(), if the unit is a
*.scope, also put it into all other cgroup controlles (cg_create() and
cg_attach()).
--
You received
Asked upstream about this: http://lists.freedesktop.org/archives
/systemd-devel/2014-November/024856.html
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syst
I have an unprivileged container setup in my test VM now, and they
continue to work with 208. However, LXC under systemd currently requires
some work (bug 1312532 and bug 1350947), so this should land first so
that system-level containers work under systemd. Then I'll look into the
cgroups issue.
11 matches
Mail list logo
