-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Unable to SSH (unable to allocate a PTY) #3424
Comments
cc @csweichel |
openssh's We haven't really come up with a solution that we're comfortable shipping in production - especially as this looks like a rather openssh specific issue. One approach is to use seccomp-notify to basically "ignore" the chown call (implemented here). Another would be to use a different SSH server, or to patch OpenSSH. As said, we haven't settled on a path forward yet. |
Thanks @csweichel that makes a lot more sense now. Do you know if there are any other SSH servers that don't do the chown in the interim? |
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. |
We announced Gitpod Local Companion last week which allows to SSH into Gitpod workspace: https://www.gitpod.io/blog/local-app Does it work for you? |
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. |
Bug description
It looks like Gitpod workspaces do not have permissions to /dev/pts
Here are the directory permissions:
Also, trying to chmod throws the same error:
This prevent connecting to Gitpod with SSH with a terminal.
Steps to reproduce
Expected behavior
No response
Example repository
https://github.com/corneliusludmann/gitpod-playground/tree/sshd-over-chisel
The text was updated successfully, but these errors were encountered: