CI integ tests failing: Running as root without --no-sandbox is not supported #3550
Labels
Comments
|
A lot of people won't switch to unprivileged mode because their working files will be unaccessible from vscode. Just give us back working --no-sandbox flag instead! |
justinmk3
added a commit
that referenced
this issue
Jun 11, 2023
Problem: Running as root causes lots of warnings, latest (fatal) example (#3550): [10429:0609/133041.674749:ERROR:network_service_instance_impl.cc(521)] Network service crashed, restarting service. 19 | [0609/133041.694037:FATAL:electron_main_delegate.cc(304)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180. Solution: - Use "run-as" directive and "export $HOME". - docker is already running, don't need "nohup /usr/local/bin/dockerd". Instead just give the user permissions to the socket: "chmod 666 /var/run/docker.sock" - remove useless things: pylint - TODO: "goenv", "go" are broken...
leigaol
pushed a commit
to leigaol/aws-toolkit-vscode
that referenced
this issue
Jun 13, 2023
Problem: Running as root causes lots of warnings, latest (fatal) example (aws#3550): [10429:0609/133041.674749:ERROR:network_service_instance_impl.cc(521)] Network service crashed, restarting service. 19 | [0609/133041.694037:FATAL:electron_main_delegate.cc(304)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180. Solution: - Use "run-as" directive and "export $HOME". - docker is already running, don't need "nohup /usr/local/bin/dockerd". Instead just give the user permissions to the socket: "chmod 666 /var/run/docker.sock" - remove useless things: pylint - TODO: "goenv", "go" are broken...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Solution
sudo code --no-sandbox --disable-gpu-sandbox ...vscode-test: disable gpu sandbox by default too microsoft/vscode-test#222The text was updated successfully, but these errors were encountered: