-
Notifications
You must be signed in to change notification settings - Fork 1.3k
ssh between workspaces #7473
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
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Currently it's possible to SSH, it's just not as easy:
Go to https://gitpod.io/workspaces, find the workspace you want to connect to, click "Connect via SSH", copy the provided command and execute the command in the workspace you want to connect from. The command should look similar to:
Given this, I will move to the IDE inbox to potentially abstract and simplify these steps Thanks @axonasif for bringing this solution to my attention! |
Hey @konne, as @atduarte mentions, you should be able to use the SSH access as if you were coming from local. However, given that you also mentioned Is it the same or similar to the use case described in this issue? Also, potentially related issues:
Depending on the use-case, a Tailscale (or similar networking) setup could also help: https://www.gitpod.io/docs/configure/tailscale |
@loujaybee I'm aware of other tickets. the SCP could be solved via a store and restore but for me, it is weird and would even not allow doing things like vscode ssh extensions there I can even browse a remote system. tailscale would solve port forwarding topics, but first I think it is too complex to set up for simple cases. Second, you do have not full control if you run multiple same workspaces in parallel. |
Describe the behavior you'd like
that I can just call:
ssh WORKSPACEID
or
scp toWORKSPACEID
between workspaces that are running and I'm the owner.
The text was updated successfully, but these errors were encountered: