When we are running our tests using chrome headless and chrome is reporting:
No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
We actually use Travis-CI to run our docker images which tests everything for us. The build that is failing is: https://travis-ci.com/rgpm/core/builds/131064462. The last successful run on Travis-CI was: https://travis-ci.com/rgpm/core/builds/130139458.
The main change that I could find was that the successful build was on Trusty, while the newer build was on Xenial. It appears that the Xenial image is missing something that the Trusty image contained.
Is this a feature or a bug? I would like to not limit our containers to Trusty as the containers are designed to run on any system. I would say that the container runs fine on my system but I know that isn’t too useful for everyone else. I can tell that the Xenial/Trusty switch happened within the past 6 days for us.