#1011066 podman fails to run with runc due to a seccomp error

Package:
runc
Source:
runc
Description:
Open Container Project - runtime
Submitter:
Francois Gouget
Date:
2022-07-04 02:33:07 UTC
Severity:
important
#1011066#5
Date:
2022-05-16 13:38:12 UTC
From:
To:
Dear Maintainer,

In Debian 11 podman depends on either crun or runc. However installing
t with runc (which docker also depends on), results in an unusable
configuration:

# podman run --rm -it debian:latest
Error: container_linux.go:367: starting container process caused: error adding seccomp filter rule for syscall bdflush: permission denied: OCI permission denied

This error prevents 'podman run' from working, both when started from a
regular account and when started as root.

A fix is to install crun (and optionally uninstall runc).
So either podman should be made to work with runc, or it should not
accept runc as an alternative to crun.