[CRIU] New docker failure
Tycho Andersen
tycho.andersen at canonical.com
Wed Dec 30 19:44:38 PST 2015
Hi Ross,
On Wed, Dec 30, 2015 at 12:11:10PM +0300, Pavel Emelyanov wrote:
> On 12/29/2015 07:00 PM, Ross Boucher wrote:
> > This isn't something I've seen before. It showed up after my latest rebase. I'm looking into it, but I thought I'd paste the log here in case someone recognizes the issue:
> >
> > https://gist.github.com/boucher/a64b611229ebe1a117f0
>
> That's likely the kernel issue -- EINVAL from ptrace(PTRACE_O_SUSPEND_SECCOMP)
> means seccomp suspending is not in the kernel.
Yep, it looks like your container is using seccomp, but your kernel
doesn't support suspending and resuming seccomp. Using any kernel
after 4.4-rc1 should be ok. (Alternatively, you can disable seccomp
for the container.)
Tycho
More information about the CRIU
mailing list