Chrome crashes on Ubuntu 16.04 inside of container

[sven-carstens]

Meta -

Image(s):
selenium/node-chrome

Images where build on the host itself and where also tested with save/load from an existing Ubuntu 14.04 instance. Both cases failed.

Docker Version:
1.12.6 (Ubuntu repo)/ 17.03.0 (Docker repo)

OS:
Ubuntu 16.04.2 / Othe CI Instance with Ubuntu 14.04 has no problems.

If the issue is with Google Chrome consider logging an issue with chromedriver instead:
https://sites.google.com/a/chromium.org/chromedriver/help

Error does not occur when using chrome on the docker host itself instead of inside of the container.

Expected Behavior -

ChromeDriver can start chrome and run the tests.

Actual Behavior -

ChromeDriver fails to start chrome.

unknown error: Chrome failed to start: crashed (Driver info: chromedriver=2.27.440175 (9bc1d90b8bfa4dd181fbbf769a5eb5e575574320),platform=Linux 4.4.0-65-generic x86_64)

Starting chrome itself does not work inside of the container.

sven.carstens@ci02:~$ docker run --rm -ti --entrypoint bash selenium/node-chrome
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

seluser@405b36b1a7c1:/$ xvfb-run /opt/google/chrome/chrome
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but >failed: errno = Operation not permitted
Illegal instruction (core dumped)
seluser@405b36b1a7c1:/$

[sven-carstens]

When I disable the security settings for docker via --security-opt seccomp:unconfined (found in http://blog.johngoulah.com/2016/03/running-strace-in-docker/) the container works fine.

Which specific permissions are missing to run properly on Ubuntu 16 ?
Just disabling everything seems a little over the top.

[sven-carstens]

Applying the seccomp configuration from this blogpost also gets chrome working again
https://github.com/jessfraz/blog/blob/master/content/post/how-to-use-new-docker-seccomp-profiles.md