On 15 May 2015 at 10:15, Lennart Poettering wrote:
> On Fri, 15.05.15 10:10, Felipe Sateler (fsate...@debian.org) wrote:
>
>> > You appear to be using a systemd version without seccomp compiled in,
>> > hence you won't get the container behaviour described, and you need to
>> > disable audit in th
On Fri, 15.05.15 10:10, Felipe Sateler (fsate...@debian.org) wrote:
> > You appear to be using a systemd version without seccomp compiled in,
> > hence you won't get the container behaviour described, and you need to
> > disable audit in the kernel instead.
>
> So, to make sure I understood corre
On 15 May 2015 at 07:31, Lennart Poettering wrote:
>
> On Sun, 10.05.15 11:20, Felipe Sateler (fsate...@debian.org) wrote:
>
> > Hi,
> >
> > I'm having a problem with a systemd-nspawn'ed container. The guest
> > journal will not start and thus I have no logs.
> >
> > The host is a 215 Debian Jessi
On Sun, 10.05.15 11:20, Felipe Sateler (fsate...@debian.org) wrote:
> Hi,
>
> I'm having a problem with a systemd-nspawn'ed container. The guest
> journal will not start and thus I have no logs.
>
> The host is a 215 Debian Jessie system. The guest is a 219 Debian Sid system.
>
> The nspawn uni
Hi,
I'm having a problem with a systemd-nspawn'ed container. The guest
journal will not start and thus I have no logs.
The host is a 215 Debian Jessie system. The guest is a 219 Debian Sid system.
The nspawn unit is at http://paste.debian.net/173849/
The host journal log for the systemd process
