https://bugzilla.suse.com/show_bug.cgi?id=1182451 https://bugzilla.suse.com/show_bug.cgi?id=1182451#c34 --- Comment #34 from Fabian Vogt --- (In reply to Frederic Crozat from comment #32)

(In reply to Michael Matz from comment #31)

...

(In reply to Frederic Crozat from comment #30)

...

...

Google and http://docs.podman.io/en/latest/markdown/podman-run.1.html tells me it's ���security-opt=seccomp=unconfined for podman.

unfortunately --security-opt=seccomp=unconfined (which is the proper syntax) works with "podman run" but doesn't do anything with "podman build" :(

I see. According to http://docs.podman.io/en/latest/markdown/podman-build.1.html I read that the seccomp option is supposed to be supported with 'build', so I'd consider this another podman bug.

I just tried to update podman on SLE15 SP2 to version 3.0.2 => no change.

However, updating runc to version v1.0.0~rc93 (with podman 2.1.1 from SLE15 SP2) fixed the issue completely.

Aleksa, should I open a SLE15 SP2 bug to get runc either updated or at least, with the seccomp fix backported ?

No response, which I'd say means "yes" in this case. -- You are receiving this mail because: You are on the CC list for the bug.