3 ms·
There have been issues[1] with seccomp. Maybe try with seccomp disabled for that container? --security-opt seccomp:unconfined More info here[2]. [1]: https
by stock_toaster 5y ago
There have been issues[1] with seccomp. Maybe try with seccomp disabled for that container?
--security-opt seccomp:unconfined
More info here[2].
[1]: https://github.com/docker/for-linux/issues/738 https://github.com/docker/for-linux/issues/738
[2]: http://mamememo.blogspot.com/2020/05/cpu-intensive-rubypython-code-runs.html http://mamememo.blogspot.com/2020/05/cpu-intensive-rubypytho...
- viraptor 5y agoseccomp affects syscalls only, which this code doesn't really use. May be worth checking just in case, but it's extremely unlikely that's the issue.
- stock_toaster 5y agoI thought it also turned on/off spectre/meltdown mitigations (impacts branch prediction) on vulnerable cpus.
- viraptor 5y agoSo TIL turning on seccomp by default turns on mitigations as well. This is not explicitly documented in Docker and it does have the possibility to opt out but doesn't. https://www.phoronix.com/scan.php?page=article&item=linux-420wip-stibp&num=1 https://www.phoronix.com/scan.php?page=article&item=linux-42...