Can't get folder inode inside docker container

[bartoszek]

I’m experiencing some issues with the Travis docker infrastructure.
Calling ls -i or stat inside the archilinux docker image results in Operation not permitted while on my local machine it works fine {os:archlinux,docker:19.03}.
Here’s some tests I’ve made
And the errors they causes
This prevents me from building lib3ds wich has this crazy check in the configure

ac_pwd=`pwd` && test -n "$ac_pwd" &&
ac_ls_di=`ls -di .` &&
ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` ||
  { echo "$as_me: error: Working directory cannot be determined" >&2

[native-api]

Ptrace doesn't work in Docker in Xenial and Bionic

Long story short, in Trusty, Docker’s default seccomp profile is not enabled as it should – that’s why it happens to work. In later distributions where that’s fixed, you need to explicitly give the container any additional privileges that it requires.

Setsockopt behaves strangely, process_vm_readv and ptrace don't work in Docker

Googling “docker process_vm_readv” shows that this is a Docker’s security feature: https://docs.docker.com/engine/security/seccomp/ I can’t find a docker run command in your build log so can’t say if anything changed there.

Find out which system call is responsible for that and give the container the necessary permissions.

[bartoszek]

Thanks, now it’s so oblivious
For the time being, I’ve added --privileged to docker run here to have the Arch-Linux container behave congruent with local system build.

[native-api]

You can see system calls with strace. It will make it clear which one returns “operation not permitted”.

[bartoszek]

Thanks Already did this. Smal caveat was that to be able to use strace inside a container I have to first add CAP_SYS_PTRACE capability to docker run.