Boot the browser image with the drukbox base entrypoint - #698
Merged
Merged
Conversation
czpython
force-pushed
the
browser-base-entrypoint
branch
from
September 22, 2026 22:37
3455903 to
9dc4e50
Compare
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 browser entrypoint starts Xvfb and x11vnc, then hands the boot to the drukbox base entrypoint. Its own copy of the base boot is gone: the SSH key for the
druksuser, the caller env, the host keys, and sshd all come from the base, which seeds the user named inDRUKBOX_SSH_USER(czpython/drukbox#54). The base digest moves to the release that carries the change.deploy/browser/goss.yamlstates the image's boot contract: thedrukskey file, sshd, Xvfb, x11vnc, port 22, and port 5900 on loopback only. The browser image job checks it with dgoss, the same way the sandbox job does in #697.