Seed the SSH user drukbox names in the local sandbox entrypoint - #54
Merged
Merged
Conversation
czpython
force-pushed
the
seed-ssh-user
branch
from
September 22, 2026 22:11
f014c6e to
ceefca4
Compare
This was referenced Sep 22, 2026
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 docker provider passes
DOCKER_SSH_USERNAMEinto the container asDRUKBOX_SSH_USER, a reserved key besideDRUKBOX_AUTHORIZED_KEY. The local sandbox entrypoint seeds that user'sauthorized_keys, root by default. A user the image does not have fails the boot with a message. A derived image that adds its own user setsDOCKER_SSH_USERNAMEand keeps the stock entrypoint. The api-tests job boots such an image and checks the seeded key.