On Tue, Dec 12, 2017 at 11:00:01PM -0600, Serge Hallyn wrote:
> On Tue, Dec 05, 2017 at 05:20:32PM +0100, Dirk Geschke wrote:
> > Hi Serge,
> >
> > > > I am a little bit clueless, I have several systems running with
> > > > Debian and unprivileged LXC. But newer systems won't start new
> > > > con
Hi Serge,
just forgot to mention: I'm using sysv-init on the host, not systemd...
Best regards
Dirk
> > > If you build without cgmanager, and your system has the cgroups
> > > individually mounted under /sys/fs/cgroup, then cgfsng will be
> > > automatically used.
>
> I just tested it by compi
Hi Serge,
> > If you build without cgmanager, and your system has the cgroups
> > individually mounted under /sys/fs/cgroup, then cgfsng will be
> > automatically used.
I just tested it by compiling and installing lxcfs. If I add to
/etc/pam.d/common-session and /etc/pam.d/common-session-noninte
Hi Serge,
> > no, lxc-2.1.1 shows a similar problem. It hangs, too, but it tries
> > to send a command in one thread and to receive it in another (afair).
> >
> > But what is cgfsng? How can I use find and use this?
>
> If you build without cgmanager, and your system has the cgroups
> individual
Quoting Dirk Geschke (d...@lug-erding.de):
> Hi Serge,
>
> > > just for the record, lxc-2.0.8 is still working this way, but it
> > > stops starting with lxc-2.0.9 and the whole lxc-2.1.x branch.
> > >
> > > I have no idea, what happened to break it nor do I have any clue
> > > to fix it. But sin
Hi Serge,
> > just for the record, lxc-2.0.8 is still working this way, but it
> > stops starting with lxc-2.0.9 and the whole lxc-2.1.x branch.
> >
> > I have no idea, what happened to break it nor do I have any clue
> > to fix it. But since I like to use unprivileged containers, it
> > would be
> You can see whether lxc-2.1.1 fixes it for you, or
It won't.
> you can run wigh cgfsng instead of cgmanager, as your
> problem is just with the cgm_lock.
>
> > Can I help in any way?
I've appened a patch to this mail which I think solves your problem. If
you could apply it and test that would
Quoting Dirk Geschke (d...@lug-erding.de):
> Hi Christian,
>
> > > > Older liblxc version used system() instead of run_command(). For
> > > > system() POSIX leaves it unspecified whether pthread_atfork() handlers
> > > > are called but glibc's implementation of system() guarantees that they
> > >
Hi Christian,
> > > Older liblxc version used system() instead of run_command(). For
> > > system() POSIX leaves it unspecified whether pthread_atfork() handlers
> > > are called but glibc's implementation of system() guarantees that they
> > > are not. But there's no requirement. So this might be
On Wed, Dec 13, 2017 at 09:22:11AM -0600, Serge Hallyn wrote:
> Quoting Christian Brauner (christian.brau...@mailbox.org):
> > On Tue, Dec 12, 2017 at 11:00:01PM -0600, Serge Hallyn wrote:
> > > On Tue, Dec 05, 2017 at 05:20:32PM +0100, Dirk Geschke wrote:
> > > > Hi Serge,
> > > >
> > > > > > I a
On Wed, Dec 13, 2017 at 01:35:01PM +0100, Christian Brauner wrote:
> On Wed, Dec 13, 2017 at 12:54:04PM +0100, Christian Brauner wrote:
> > On Tue, Dec 12, 2017 at 11:00:01PM -0600, Serge Hallyn wrote:
> > > On Tue, Dec 05, 2017 at 05:20:32PM +0100, Dirk Geschke wrote:
> > > > Hi Serge,
> > > >
>
On Wed, Dec 13, 2017 at 12:54:04PM +0100, Christian Brauner wrote:
> On Tue, Dec 12, 2017 at 11:00:01PM -0600, Serge Hallyn wrote:
> > On Tue, Dec 05, 2017 at 05:20:32PM +0100, Dirk Geschke wrote:
> > > Hi Serge,
> > >
> > > > > I am a little bit clueless, I have several systems running with
> > >
On Tue, Dec 12, 2017 at 11:00:01PM -0600, Serge Hallyn wrote:
> On Tue, Dec 05, 2017 at 05:20:32PM +0100, Dirk Geschke wrote:
> > Hi Serge,
> >
> > > > I am a little bit clueless, I have several systems running with
> > > > Debian and unprivileged LXC. But newer systems won't start new
> > > > con
On Tue, Dec 05, 2017 at 05:20:32PM +0100, Dirk Geschke wrote:
> Hi Serge,
>
> > > I am a little bit clueless, I have several systems running with
> > > Debian and unprivileged LXC. But newer systems won't start new
> > > containers.
> > >
> > > Actually I have a Debian stretch, installed the norm
Quoting Dirk Geschke (d...@lug-erding.de):
> Hi Serge,
>
> > > I am a little bit clueless, I have several systems running with
> > > Debian and unprivileged LXC. But newer systems won't start new
> > > containers.
> > >
> > > Actually I have a Debian stretch, installed the normal way but
> > > wi
Hi Serge,
> > I am a little bit clueless, I have several systems running with
> > Debian and unprivileged LXC. But newer systems won't start new
> > containers.
> >
> > Actually I have a Debian stretch, installed the normal way but
> > with lxc-2.0.9 and cgmanager-0.41 installed from sources.
> >
Quoting Dirk Geschke (d...@lug-erding.de):
> Hi all,
>
> I am a little bit clueless, I have several systems running with
> Debian and unprivileged LXC. But newer systems won't start new
> containers.
>
> Actually I have a Debian stretch, installed the normal way but
> with lxc-2.0.9 and cgmanager
Hi all,
>
> I am a little bit clueless, I have several systems running with
> Debian and unprivileged LXC. But newer systems won't start new
> containers.
>
> Actually I have a Debian stretch, installed the normal way but
> with lxc-2.0.9 and cgmanager-0.41 installed from sources.
hmm, strange,
Hi all,
I am a little bit clueless, I have several systems running with
Debian and unprivileged LXC. But newer systems won't start new
containers.
Actually I have a Debian stretch, installed the normal way but
with lxc-2.0.9 and cgmanager-0.41 installed from sources.
I can setup cgmanager, can d
19 matches
Mail list logo
