# Setsockopt behaves strangely, process\_vm\_readv and ptrace don't work in Docker

**URL:** https://travis-ci.community/t/setsockopt-behaves-strangely-process-vm-readv-and-ptrace-dont-work-in-docker/5075
**Category:** Linux
**Tags:** build-env
**Created:** [September 12, 2019, 6:21pm UTC](https://travis-ci.community/t/setsockopt-behaves-strangely-process-vm-readv-and-ptrace-dont-work-in-docker/5075 "2019-09-12T18:21:11Z")
**Posts on this page:** 1
**Showing post:** 4

<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: [September 13, 2019, 8:47pm UTC](https://travis-ci.community/t/setsockopt-behaves-strangely-process-vm-readv-and-ptrace-dont-work-in-docker/5075/4 "2019-09-13T20:47:02Z")

</div>

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.

---

_[View the full topic](https://travis-ci.community/t/setsockopt-behaves-strangely-process-vm-readv-and-ptrace-dont-work-in-docker/5075)._