Solved Connecting to FreeBSD from VS Code over SSH

Jiri · Nov 6, 2024

Hi guys,

I'm trying to figure out how to connect to my FreeBSD box from VS Code over SSH. There are some instructions here and here, but I haven't had much luck following those.

Client
Pop!_OS (based on Ubuntu 22.04)
VS Code 1.95.0

VS Code extension Remote - SSH v0.116.2024102915 (pre-release)
Remote.SSH: Enable Remote Command is enabled.

~/.ssh/config:

Code:

Host beastie1
  Hostname beastie1
  User jiri
  RemoteCommand /compat/linux/usr/bin/bash

Server
FreeBSD 14.1

linux service is running

Code:

# service -e | grep linux
linux/etc/rc.d/linux

Code:

/compat/linux/usr/bin/uname -a
Linux beastie1 5.15.0 FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC x86_64 x86_64 x86_64 GNU/Linux

VS Code creates ~/.vscode-server dir (empty) on first attempt to connect.

Remote - SSH extension output (truncated):

Code:

[13:01:34.946] stderr> Authenticated to beastie1 ([192.168.0.161]:22) using "publickey".
[13:01:35.001] > ready: 0f751ff52673
[13:01:35.009] > FreeBSD 14.1-RELEASE FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC
[13:01:35.009] Platform: linux
[13:01:35.015] > /usr/local/bin/zsh
[13:01:35.015] Parent Shell: zsh
[13:01:35.015] Parent Shell pid: 122712
[13:01:35.021] > 3128
[13:01:35.021] Waiting for pid of spawned 'sh' subshell: '3128'...
[13:01:35.038] > 0f751ff52673: running
> Script executing under PID: 3128
[13:01:35.045] > Unsupported platform: FreeBSD

My primary shell on the server is zsh, but it shouldn't be an issue, because I'm explicitly telling VS Code to use /compat/linux/usr/bin/bash.

Any ideas?

Jiri · Nov 6, 2024

Fixed, sorry.

~/.ssh/config:

Code:

Host beastie1
  RemoteCommand /compat/linux/usr/bin/bash

vedran · Nov 6, 2024

Jiri said:
There are some instructions here.

Thanks for the mention! Glad you got it working with some tweaking.

Jiri · Nov 6, 2024

vedran said:
Thanks for the mention! Glad you got it working with some tweaking.

Oh, thank you for the tutorial! And I love that the admins approved the thread even though I had already answered it before they did.

Maybe one more detail for people stumbling upon this in the future: the extension's Remote.SSH: Enable Remote Command option doesn't seem to be doing anything, I've turned it off just to see what happens, and it still works.