Connecting to workspaces using SSH without the coder CLI #25525
|
Either I've missed something obvious or is it correct that there is no way to connect to a workspace using SSH natively? I know the general file transfer is possible by using the filebrowser module and the browser, but that would also imply having another tool to look over. |
Replies: 2 comments 3 replies
|
You should run the |
|
That's what I thought as well, but the created config uses # ------------START-CODER-----------
# This section is managed by coder. DO NOT EDIT.
#
# You should not hand-edit this section unless you are removing it, all
# changes will be lost when running "coder config-ssh".
#
Host coder.*
ConnectTimeout=0
StrictHostKeyChecking=no
UserKnownHostsFile=/dev/null
LogLevel ERROR
ProxyCommand /usr/bin/coder --global-config /home/dummy/.config/coderv2 ssh --stdio --ssh-host-prefix coder. %h
Host *.coder
ConnectTimeout=0
StrictHostKeyChecking=no
UserKnownHostsFile=/dev/null
LogLevel ERROR
Match host *.coder !exec "/usr/bin/coder connect exists %h"
ProxyCommand /usr/bin/coder --global-config /home/dummy/.config/coderv2 ssh --stdio --hostname-suffix coder %h
# ------------END-CODER------------ |
Outside of the browser workspace apps you mentioned (there's also the web terminal), this isn't possible. |
|
Though I suppose there'd be nothing stopping you from writing templates whose workspaces make themselves available without the use of Coder's networking. |
|
Thanks for the confirmation. I was hoping I missed something, but the way coder is designed the current limitation "makes sense". |
Outside of the browser workspace apps you mentioned (there's also the web terminal), this isn't possible.
You'll either need the Coder CLI installed for
coder ssh/coder config-ssh, or Coder Desktop for macOS or Windows, which makes your workspaces available system-wide via a.coderhostname.