I've made separate Bug #1467611 as requested.
--
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/1413927
Title:
user lxc containers fail to start under systemd: login name=sys
Daniel [2015-05-20 16:19 -]:
> Is this bug really fixed? I have very similar errors with the version
> from the vivid live cd (systemd 219-7ubuntu3) when trying to start user-
> space LXC containers
I haven't tried creating/running containers on a live system, as that
environment is quite a bi
Is this bug really fixed? I have very similar errors with the version
from the vivid live cd (systemd 219-7ubuntu3) when trying to start user-
space LXC containers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubu
This bug was fixed in the package systemd - 218-6ubuntu1
---
systemd (218-6ubuntu1) vivid; urgency=medium
* Merge with Debian unstable. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
/etc/writable/ instead.
- Keep our much
Quoting Martin Pitt (martin.p...@ubuntu.com):
> Stéphane Graber [2015-01-25 17:15 -]:
> > How are we supposed to run a systemd container on such a system then?
> >
> > systemd in a container will need to create sub-entries in the
> > name=systemd controller.
>
> Yes, that works fine, as the c
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
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/1413927
Title:
user lxc containers fail to start
Hmm, so here the user didn't own the directories which was a good part
of the issue I suspect.
--
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/1413927
Title:
user lxc conta
Stéphane Graber [2015-01-25 17:15 -]:
> How are we supposed to run a systemd container on such a system then?
>
> systemd in a container will need to create sub-entries in the
> name=systemd controller.
Yes, that works fine, as the cgroup *directories* are owned by the
user. I just don't want
Oh and the same goes for containers that aren't running systemd but are
running logind as logind also expects to be able to create sub-entries
in the name=systemd controller, which with the current cgroup ownership,
it won't be able to do.
--
You received this bug notification because you are a m
How are we supposed to run a systemd container on such a system then?
systemd in a container will need to create sub-entries in the
name=systemd controller. If the user doesn't own its cgroup, LXC will
not be able to create the entry for the container and the container will
not be able to write to
10 matches
Mail list logo
