-
-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Headless system crashes with SIGSEVG when starting app #365
Comments
Exploring a little more with this, I've tried exec'ing into the container, and when I first ran
Digging around, it appears there's a missing driver, so adding this to a Dockerfile got me past that:
Now when I run the startup script, it gets a little further, and actually writes out to the handbrake debug log:
Adding this to the Dockerfile fixes the
But then I get this in the hb debug log:
My leading theory is that this is related to the host running Wayland and the container attempting to exist in X11, and for some reason there isn't true isolation between the host and container. I'll continue to dig. Could also be related to using the |
This container doesn't need anything from the host for display purpose. So you should definitely not set the The Do you see the same crash if you run |
Current Behavior
I'm not entirely sure what specifically is incorrect, or if anything, however I'm running a headless Ubuntu 22.04 box with docker, and though I connect to it with the Microsoft RDP client (since VNC no longer works on Ubuntu), I generally don't have a display connected.
When starting the app, I get an endless loop of errors:
After some sleuthing:
xhost
and runningxhost +
:xhost: unable to open display ""
/startapp.sh
:(fr.handbrake.ghb:20718): Gtk-WARNING **: 11:48:57.696: Failed to open display
I realized that there's no
DISPLAY
set, since there's no GUI session on the host. I tried addingDISPLAY=${DISPLAY}
to my docker-compose file, and this got it a little further, but now xvnc is still failing to load:Expected Behavior
There should be a way to configure the system to handle headless hosts (or perhaps I am doing something uniquely weird, and this is an RDP issue not a headless issue).
Steps To Reproduce
linuxbrew
(not Docker Desktop)And based on this Dockerfile:
Environment
Container creation
(See in ^ repro)
Container log
Container inspect
The text was updated successfully, but these errors were encountered: