Arch Linux

Gregosky

Member

From: UK

Registered: 2013-07-26

Posts: 174

[SOLVED] glibc & podman - where does podman get seccomp.json from

I'm facing weird issue with podman, which I learned today has something to do with glibc. This github issue describes it well: https://github.com/containers/podman/issues/9725

In short this works:

docker run -it --rm docker.io/library/archlinux /bin/bash -c '[ -r /etc/fstab ] && echo "!"' # prints '!'

While this does not work as intended:

podman run -it --rm docker.io/library/archlinux /bin/bash -c '[ -r /etc/fstab ] && echo "!"' # does not print '!'

The author of the issue points at some problems with glibc and links this issue: https://github.com/containers/crun/issues/646 suggesting it resolves his problem - but I checked seccomp.json in my installation and it's almost identical as what is linked in the issue ("almost" - there was one line that was different however that line did not seem to contribute to solving the problem).

Is there anybody here who faced this issue and knows how to apply the seccomp.json solution to fix this? Thanks!

Last edited by Gregosky (2021-09-07 14:08:34)

Gregosky

Member

From: UK

Registered: 2013-07-26

Posts: 174

Re: [SOLVED] glibc & podman - where does podman get seccomp.json from

Looks like switching podman to runc is fixing my problem.