Boot the sandbox image with the drukbox base entrypoint - #697
Merged
Merged
Conversation
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 drukbox base entrypoint seeds the SSH user named in
DRUKBOX_SSH_USER(czpython/drukbox#54), and the install runs drukbox withDOCKER_SSH_USERNAME=druks. The sandbox image keeps itsuseradd druksand drops its own entrypoint, so the base entrypoint boots it: the SSH key, the caller env, the secrets-proxy CA, and theghgit credential all come from the base. The base digest moves to the release that carries the change.deploy/sandbox/goss.yamlstates the image's boot contract: thedrukskey file, sshd, port 22. The image job checks it with dgoss in place of the shell boot step. The CA install and the git helper are base behavior; this image adds nothing to them.The browser image keeps its entrypoint for the display stack.