[systemd-devel] Systemd 215 cannot start journald 219 inside systemd-nspawn

Lennart Poettering lennart at poettering.net
Fri May 15 06:15:08 PDT 2015

On Fri, 15.05.15 10:10, Felipe Sateler (fsateler at 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 correctly: does this have anything to do
> with 215/219 interop or is just that 219 wants to use audit and it is
> broken? I gather it is the latter but confirmation would be nice. In
> other words, would running 219 in the host fix anything, or should we
> expect all Debian 219 containers to fail?

Yeah, 219 uses the audit mcast stuff, which it previously didn't
use. But generally audit is borked in containers, you have to turn it
off anyway to use containers properly. Or you run x86-64 and compile
with libseccomp...


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list