-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/run: Add flag --no-tty/-T to run command. #587
Open
likan999
wants to merge
1
commit into
containers:main
Choose a base branch
from
likan999:patch-5
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
Build failed.
|
Build failed.
|
Build failed.
|
likan999
added a commit
to likan999/ppa-toolbox
that referenced
this pull request
Oct 30, 2020
Summary: VSCode remote SSH extension needs to run commands inside toolbox without a TTY, otherwise it fails. With this patch, vscode can connect to toolbox in a remote host if you put `RemoteCommand toolbox run -T bash` in ssh config; it should work as well if using `authorized_keys` instead. The naming of `-T` option is borrowed from `ssh -T`. containers#587
Build failed.
|
likan999
added a commit
to likan999/ppa-toolbox
that referenced
this pull request
Oct 30, 2020
Summary: VSCode remote SSH extension needs to run commands inside toolbox without a TTY, otherwise it fails. With this patch, vscode can connect to toolbox in a remote host if you put `RemoteCommand toolbox run -T bash` in ssh config; it should work as well if using `authorized_keys` instead. The naming of `-T` option is borrowed from `ssh -T`. containers#587
likan999
added a commit
to likan999/ppa-toolbox
that referenced
this pull request
Oct 30, 2020
Summary: VSCode remote SSH extension needs to run commands inside toolbox without a TTY, otherwise it fails. With this patch, vscode can connect to toolbox in a remote host if you put `RemoteCommand toolbox run -T bash` in ssh config; it should work as well if using `authorized_keys` instead. The naming of `-T` option is borrowed from `ssh -T`. containers#587
Build failed.
|
likan999
added a commit
to likan999/ppa-toolbox
that referenced
this pull request
Oct 30, 2020
Summary: VSCode remote SSH extension needs to run commands inside toolbox without a TTY, otherwise it fails. With this patch, vscode can connect to toolbox in a remote host if you put `RemoteCommand toolbox run -T bash` in ssh config; it should work as well if using `authorized_keys` instead. The naming of `-T` option is borrowed from `ssh -T`. containers#587
likan999
added a commit
to likan999/ppa-toolbox
that referenced
this pull request
Oct 30, 2020
Summary: VSCode remote SSH extension needs to run commands inside toolbox without a TTY, otherwise it fails. With this patch, vscode can connect to toolbox in a remote host if you put `RemoteCommand toolbox run -T bash` in ssh config; it should work as well if using `authorized_keys` instead. The naming of `-T` option is borrowed from `ssh -T`. containers#587
Build failed.
|
likan999
added a commit
to likan999/ppa-toolbox
that referenced
this pull request
Oct 30, 2020
Summary: VSCode remote SSH extension needs to run commands inside toolbox without a TTY, otherwise it fails. With this patch, vscode can connect to toolbox in a remote host if you put `RemoteCommand toolbox run -T bash` in ssh config; it should work as well if using `authorized_keys` instead. The naming of `-T` option is borrowed from `ssh -T`. containers#587
Closed
likan999
added a commit
to likan999/ppa-toolbox
that referenced
this pull request
Nov 4, 2020
Summary: VSCode remote SSH extension needs to run commands inside toolbox without a TTY, otherwise it fails. With this patch, vscode can connect to toolbox in a remote host if you put `RemoteCommand toolbox run -T bash` in ssh config; it should work as well if using `authorized_keys` instead. The naming of `-T` option is borrowed from `ssh -T`. containers#587
changwuf31
pushed a commit
to changwuf31/toolbox
that referenced
this pull request
Dec 29, 2020
Summary: VSCode remote SSH extension needs to run commands inside toolbox without a TTY, otherwise it fails. With this patch, vscode can connect to toolbox in a remote host if you put `RemoteCommand toolbox run -T bash` in ssh config; it should work as well if using `authorized_keys` instead. The naming of `-T` option is borrowed from `ssh -T`. containers#587
Build failed.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
2. CLI
Issue is related to the command line interface
2. Host Realm
The issue is related to what happens on the host machine where Toolbox is executed
3. New Feature
New feature
6. Minor Change
Should not cause breakage
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.
VSCode remote SSH extension needs to run commands inside toolbox without a TTY, otherwise it fails. With this patch, vscode can connect to toolbox in a remote host if you put
RemoteCommand toolbox run -T bash
in ssh config; it should work as well if usingauthorized_keys
instead. The naming of-T
option is borrowed fromssh -T
.