add bass --runner for serving runtimes through SSH
#180
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
establishes an SSH connection and forwards local runtimes
otherwise no services get forwarded and the remote end tries to talk to a local buildkit instead
* show ssh command as vertex * don't log if 0 keys are found in agent
bass --forward for forwarding runtimesbass --runner for serving runtimes through SSH
|
This is revised by #186 which serves runtimes via gRPC rather than forwarding the underlying service addresses. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Experimental
Usage:
SSHes to the provided address (default port 6455) and forwards each runtime through it via a
forward --runtime <driver>command, opening a reverse Unix socket tunnel to each service address.For use with Bass Loop, but other servers could be implemented.