Skip to content

User containers.conf seccomp_profile = "unconfined" has no effect #6498

@nalind

Description

@nalind

It looks like seccomp_profile from containers.conf wasn't wired in to Run().

Discussed in #6490

Originally posted by XeCycle November 9, 2025
I'm on Arch Linux host, and running Ubuntu jammy (and later) images has problems with the shipped seccomp profile. It works with buildah from --security-opt seccomp=unconfined ubuntu:noble; setting containers.seccomp_profile = "unconfined" in ~/.config/containers/containers.conf works for podman, but not buildah. Which setting can I use with buildah so that I don't need to add those args on every call?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions