Skip to content

Disable seccomp confinement for podman builds

Anton Gerasimov requested to merge oytis/redox:fix-seccomp-podman-build into master

Problem: podman build seems to fail when seccomp is enabled on the host system. At least it fails on my Arch.

The problem manifests itself as The following signatures couldn't be verified because the public key is not available ... when building podman container, but seems to be related to seccomp confinement.

For Docker a similar problem is reported to be fixed in newer versions of Docker so that disabling seccomp confinement might not be required, but I am running a recent version of Podman (5.2.5), and it is still there, so here we are.

Solution: disable seccomp confinement for podman builds.

TODOs: maybe there is a more elegant solution, or it will stop being necessary for newer versions of podman.

State: ready

Merge request reports