Ubuntu
libseccomp package

  1. Bug #1891810
  2. Comment #0

Comment 0 for bug 1891810

Revision history for this message
Steve Dodd (anarchetic) wrote : Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers

The version of libseccomp2 in bionic does not know about the openat2 syscall.

In my particular usecase, I was trying to run podman/buildah in an nspawn container, using fuse-overlayfs. This leads to peculiar failure modes as described in this issue:

https://github.com/containers/fuse-overlayfs/issues/220

This could well cause other problems, previously issues like that have affected snapd, etc.

Backporting the master branch of libseccomp fixed this for me, but for an SRU a cherrypick of https://github.com/seccomp/libseccomp/commit/b3206ad5645dceda89538ea8acc984078ab697ab might be sufficient...

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libseccomp2 2.4.3-1ubuntu3.18.04.3
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
Date: Sun Aug 16 17:35:09 2020
Dependencies:
 gcc-8-base 8.4.0-1ubuntu1~18.04
 libc6 2.27-3ubuntu1.2
 libgcc1 1:8.4.0-1ubuntu1~18.04
ProcEnviron:
 TERM=screen.xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: libseccomp
UpgradeStatus: No upgrade log present (probably fresh install)