# Can't get folder inode inside docker container

**URL:** https://travis-ci.community/t/cant-get-folder-inode-inside-docker-container/8812
**Category:** Travis CI Discussions & Feedback
**Created:** [May 30, 2020, 8:31am UTC](https://travis-ci.community/t/cant-get-folder-inode-inside-docker-container/8812 "2020-05-30T08:31:18Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)
#### Post date: [May 30, 2020, 12:10pm UTC](https://travis-ci.community/t/cant-get-folder-inode-inside-docker-container/8812/2 "2020-05-30T12:10:08Z")

</div>

> [@Ptrace doesn't work in Docker in Xenial and Bionic](https://travis-ci.community/t/ptrace-doesnt-work-in-docker-in-xenial-and-bionic/5953/2):
>
> 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](https://travis-ci.community/t/setsockopt-behaves-strangely-process-vm-readv-and-ptrace-dont-work-in-docker/5075/4):
>
> Googling “docker process\_vm\_readv” shows that this is a Docker’s security feature: [https://docs.docker.com/engine/security/seccomp/](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.

---

_[View the full topic](https://travis-ci.community/t/cant-get-folder-inode-inside-docker-container/8812)._