feat(image): launch wayvnc inside the kiosk session for remote debug#226
Merged
privaloops merged 1 commit intomainfrom Apr 27, 2026
Merged
feat(image): launch wayvnc inside the kiosk session for remote debug#226privaloops merged 1 commit intomainfrom
privaloops merged 1 commit intomainfrom
Conversation
The kiosk runs two flights up; staring at the HDMI panel to debug Chromium isn't a feature. Add wayvnc so a VNC viewer on the LAN can mirror cage's framebuffer. Approach details: - The Debian wayvnc package ships a systemd unit that runs as a dedicated 'vnc' user. That user has no access to cage's Wayland socket and the unit silently fails while squatting port 5900. Disable it on first-boot so it doesn't fight the in-session instance. - start-kiosk.sh now wraps Chromium in `cage -d -- /bin/sh -c`, with wayvnc started in the background before the chromium exec. wayvnc inherits cage's WAYLAND_DISPLAY through the shared environment, so it gets a working screen-capture pipe. When Chromium exits, the shell exits, the cage session tears down, wayvnc's parent dies, and the listener is reaped — no zombies between kiosk restarts. - wayvnc 0.9 ships with auth disabled by default; the LAN-only exposure is acceptable for a single-tenant arcade appliance. If we later want auth, drop a ~/.config/wayvnc/config with credentials. Connect from a Mac with a real RFB client (RealVNC Viewer / TigerVNC — the macOS Screen Sharing built-in speaks an Apple dialect that wayvnc rejects).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The kiosk runs two flights up; staring at the HDMI panel to debug
Chromium isn't a feature. Add wayvnc so a VNC viewer on the LAN can
mirror cage's framebuffer.
Approach details:
dedicated 'vnc' user. That user has no access to cage's Wayland
socket and the unit silently fails while squatting port 5900.
Disable it on first-boot so it doesn't fight the in-session
instance.
cage -d -- /bin/sh -c, withwayvnc started in the background before the chromium exec. wayvnc
inherits cage's WAYLAND_DISPLAY through the shared environment, so
it gets a working screen-capture pipe. When Chromium exits, the
shell exits, the cage session tears down, wayvnc's parent dies,
and the listener is reaped — no zombies between kiosk restarts.
exposure is acceptable for a single-tenant arcade appliance. If we
later want auth, drop a ~/.config/wayvnc/config with credentials.
Connect from a Mac with a real RFB client (RealVNC Viewer / TigerVNC
— the macOS Screen Sharing built-in speaks an Apple dialect that
wayvnc rejects).