Tailscale ssh to a gitpod container: "Unable to change owner or mode of tty stdin: Operation not permitted"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
I cannot tailscale ssh into a gitpod container. I've tried several different client devices with the same result.
Authentication via tailscale ssh works, but then the tty cannot be allocated and the process fails with:
Unable to change owner or mode of tty stdin: Operation not permitted
I can tailscale ssh into other non-gitpod containers without issue.
Steps to reproduce
In a gitpod container:
- I've configured the
TAILSCALE_AUTHKEYenv var in gitpod with an ephemeral authkey - Open the gitpod https://github.com/gitpod-io/template-tailscale
- Run
tailscale upwith your authkey and the ssh flag
On another device connected to the tailnet
ssh -v gitpod@<tailnet ip for the gitpod container>
Workspace affected
all
Expected behavior
I expect to be able to SSH to the gitpod instance via tailscale
Example repository
https://github.com/gitpod-io/template-tailscale
Anything else?
I first reported this issue over at tailscale, but based on the findings of this gitpod issue it seems that this phenomenon may be a consequence of gitpod's ssh daemon + container setup.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the gitpod-io/template-tailscale example repository and reproduce the Tailscale SSH connection in a Gitpod container. Review the linked Tailscale issue and Gitpod issue 3424 for findings about the SSH daemon and container setup. Done means a Tailscale SSH session can allocate its tty without the ownership or mode error.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100