microsoft / microsoft/vscode-remote-release
can't start remote SSH when remote Linux server uses fish shell
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Type: Bug
I want to use the Remote-SSH extension to access the file system on a remote Linux server. My user account on the remote server is set up to use the fish shell https://fishshell.com/ This shell uses a different language than the regular bourne shell, typically used on Linux.
When connecting, the SSH session is created successfully, but then simply times out. I assume that VSCode sends some commands to start the remote server which use bourne shell syntax, which then fails with the fish shell.
Extension version: 0.120.0
VS Code version: Code 1.100.2 (Universal) (848b80aeb52026648a8ff9f7c45a9b0a80641e2e, 2025-05-14T21:47:40.416Z)
OS version: Darwin arm64 23.6.0
Modes:
Remote OS version: Linux x64 5.15.0-119-generic
System Info
| Item | Value |
|---|---|
| CPUs | Apple M2 (8 x 2400) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | 2, 2, 2 |
| Memory (System) | 16.00GB (0.18GB free) |
| Process Argv | --crash-reporter-id 27792d9b-e32e-4fbf-bbee-4c9d557b4aa1 |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | SSH: vm |
| OS | Linux x64 5.15.0-119-generic |
| CPUs | Intel(R) Xeon(R) Platinum 8280 CPU @ 2.70GHz (8 x 0) |
| Memory (System) | 31.27GB (28.62GB free) |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
pythonrstrctxt:31112756
nativeloc2:31192216
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
hdaa2157:31222309
copilot_t_ci:31222730
e5gg6876:31282496
pythoneinst12:31285622
bgtreat:31268568
4gafe986:31271826
c7cif404:31309971
996jf627:31283433
pythonrdcb7:31303018
usemplatestapi:31297334
0aa6g176:31307128
7bj51361:31289155
747dc170:31275177
pylancecolorcf:31309109
aj953862:31281341
generatesymbolt:31295002
convertfstringf:31295003
gendocf:31295004
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 by reproducing the Remote-SSH connection with the reported VS Code and extension versions, using a Linux account whose login shell is fish. Investigate the connection startup path and its shell assumptions. Done means the remote server starts successfully and the file system becomes accessible without timing out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fish, linux, vscode
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100