You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the runAsHostUser flag in unity-builder and unity-test-runner, xvfb-run is invoked without root privileges.
This causes the following errors: _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
How to reproduce
Run unity-builder or unity-test-runner with runAsHostUser on a self-hosted runner.
Bug description
When using the
runAsHostUser
flag in unity-builder and unity-test-runner,xvfb-run
is invoked without root privileges.This causes the following errors:
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
How to reproduce
Run unity-builder or unity-test-runner with
runAsHostUser
on a self-hosted runner.Full log
Workflow file used
Expected behavior
xvfb-run
should not throw any errors.Additional details
A similar issue is also described here and here.
It seems that adding
-nolisten unix
to the arguments that are passed to Xvfb fixes this issue.My proposal would be to add
--server-args="-nolisten unix"
to the line where the alias for the unity-editor is created:docker/images/ubuntu/editor/Dockerfile
Line 64 in 33cc94c
However, I am unsure if this change would have any unforeseen consequences.
The text was updated successfully, but these errors were encountered: