Does this run from VM? about autochrome

[RyanKoppenhaver-NCC]

I was able to reproduce this using both root and a regular user account on a Kali VM.

As a workaround, you can call chrome-wrapper with the --no-sandbox argument on the command line, or add that value to the OPTS array in /root/.local/autochrome/chrome

Looking at the Chromium source here, the error occurs when neither the namespace or suid sandboxes are available. (The suid sandbox seems to be mostly deprecated, so the namespace sandbox not working is the issue.)

I think the failing bit might be here, but I'll have to dig a bit more to see if there's a better way to fix this than just disabling the sandbox entirely.

[RyanKoppenhaver-NCC]

Looks like running sysctl kernel.unprivileged_userns_clone=1 as root will allow the namespace sandbox to work, though chromium still refuses to run as root unless --no-sandbox is set.

My tentative plan for a fix is:

1. If Autochrome is run as root, warn the user but continue
2. In Autochrome, check for unprivileged_userns_clone = 0 and prompt the user to set it to 1.
3. In the wrapper, use --no-sandbox if the user is root or unprivileged_userns_clone is 0.