Presumably via /usr/bin/runc.
```
# ldd /usr/bin/runc
linux-vdso.so.1 (0x003940e63000)
libseccomp.so.2 => /lib/riscv64-linux-gnu/libseccomp.so.2
(0x003940e3a000)
libc.so.6 => /lib/riscv64-linux-gnu/libc.so.6 (0x003940cba000)
I confirm that this also affects Noble.
If libseccomp2 is >= 2.55, then Docker must be >= 25.0.3.
I looked at fixing the Docker profile, and this works for `docker run`,
but `docker build` always uses the build-in/default profile, so it's a
limited workaround.
--
You received this bug
I did some analysis
[here](https://github.com/ocaml/infrastructure/issues/121).
libseccomp needs to be >= 2.55 and Docker >= 25.0.3 and then this issue
goes away. Without these the system call `fchmodat2` return EPERM
rather than `ENOSYS`.
** Bug watch added:
If you compile tar from scratch within the Docker container, then you do
not see the error.
```
wget https://ftp.gnu.org/gnu/tar/tar-1.35.tar.gz
tar -xzf tar-1.35.tar.gz
```
Ignore the errors from the tar process :-)
```
apt install build-essential libacl1-dev -y
cd tar-1.35
This also affects ppc64le Docker images. These commands work fine on
x86_64, arm64 and s390 but fail on POWER9.
```
docker run -it --rm ubuntu:noble
apt-get -y update
apt install -y wget
cd /tmp
wget a-tar-file-of-your-choice.tar.gz
tar -xzf a-tar-file-of-your-choice.tar.gz
```
Error message:
