On 08/12/2020 22:21, Ben Green wrote:
It's that pesky systemd isn't it? I've made a script to get things
back to how we want which looks like this for the guest ${1}:
To add some info to this, I've confirmed that running 'systemctl
daemon-reload' causes systemd to move all pids into it's
On 22/11/2020 15:09, Serge E. Hallyn wrote:
Can you cat /proc/$pid/cgroup for one of the tasks in an autostarted container,
and show the /var/lib/lxc/container-name/config ?
I must apologise for such a later response, this is the first time I've
been back to this problem since you responded.
Dear Ben, (hi Serge,)
maybe you should also take a look what happens if you play with namespaces
using the userland tools like lsns, unshare and enterns .
with greetings
Guido
On 2020-11-22 16:09, Serge E. Hallyn wrote:
> Can you cat /proc/$pid/cgroup for one of the tasks in an autostarted
>
On Sun, Nov 22, 2020 at 01:41:14PM +, Ben Green wrote:
> On 21/11/2020 21:54, Serge E. Hallyn wrote:
> > I've never used lxc-autostart, but looking at the manpage, do you
> > have lxc.start.auto set in the containers you want to start? What
> > do the configs look like?
> >
> > Do the
On 21/11/2020 21:54, Serge E. Hallyn wrote:
I've never used lxc-autostart, but looking at the manpage, do you
have lxc.start.auto set in the containers you want to start? What
do the configs look like?
Do the containers actually start but in the wrong cgroup? Or do
they just not start?
They
On Sat, Nov 21, 2020 at 09:25:15PM +, Ben Green wrote:
> Hi all,
>
> I've been wrestling with cgroups for ages, trying to get limits applied to
> containers. I've created a directories 'forcontainers' which exist in
> /sys/fs/cgroup/*/forcontainers/ on the advice of Serge E. Hallyn. It works
Hi all,
I've been wrestling with cgroups for ages, trying to get limits applied
to containers. I've created a directories 'forcontainers' which exist in
/sys/fs/cgroup/*/forcontainers/ on the advice of Serge E. Hallyn. It
works perfectly well during normal operation but I can't find a way to
