I’m hoping this is a FAQ, but I haven’t been able to track it down.
Running Docker 17.03.1-ce-win12(12058) on a Windows 10 host, my problem is reproducible with a very simple container containing basically nothing but Centos 7.3.
On my Windows containers, my Centos images come up with kernel option kernel.yama.ptrace_scope set to 1.
If I run the same container on a Linux host, that kernel option is not even present.
I don’t quite understand how kernel options are different when instantiating a container in two different places, but I’m guessing this is controlled maybe by the daemon configuration file?
Can anybody point me to the place in the docs where this is explained?
Containers employ operating system virtualization which means that the host kernel is shared between all containers running on a host and they all see the kernel (and the settings) of that particular host.
Containers employ operating system virtualization which means that the host kerne
Right I guess the reason this is less obvious on Windows is that the host kernel is kind of invisible and maybe less amenable to configuration.
I realize that there is a huge amount of traffic on the ptrace problem in the github issues, so I have achieved some understanding of it, and have also seemed to recreate all the dead ends that users have run into trying to resolve this.