Closed ItsMeBrianD closed 2 months ago
Hi @ItsMeBrianD, thanks for opening the issue. Did you symlink /bin/sh
to /bin/fish
(or wherever fish is installed) by chance?
On the remote host, I did not, fish is only at /usr/bin/fish
I'm asking because we run the command with sh -c
, not sure why it's executed in the fish shell
Here's some more system detail:
Let me know if there's anything else that would help track this down, happy to help however I can
@ItsMeBrianD I can reproduce the issue, I'm just not entirely sure where the problem lies. Will take another look but for now it's rather low priority tbh
I'm also affected:
What happened?
I created an SSH provider, using a remote machine which uses fish shell. The agent isn't properly injected.
What did you expect to happen instead?
The agent is properly injected, starts and the workspace opens in the selected IDE.
How can we reproduce the bug? (as minimally and precisely as possible)
Debug logs:
[11:07:54] info Workspace vscode-remote-try-go already exists
[11:07:54] debug Acquire workspace lock...
[11:07:54] debug Acquired workspace lock...
[11:07:54] info Creating devcontainer...
[11:07:54] debug Inject and run command: '/tmp/devpod/agent' helper ssh-server --stdio --debug
[11:07:54] debug Attempting to create SSH client
[11:07:54] debug execute inject script
[11:07:54] debug download agent from https://github.com/loft-sh/devpod/releases/download/v0.5.4
[11:07:54] debug Run command provider command: ${SSH_PROVIDER} command
[11:07:55] debug done exec
[11:07:55] debug done inject
[11:07:55] debug done injecting
[11:07:55] debug Inject Error: fish: Unsupported use of '='. In fish, please use 'set INSTALL_DIR "/tmp/devpod"'.
INSTALL_DIR="/tmp/devpod"
^~~~~~~~~~~~~~~~~~~~~~~~^
EOF
It tries to inject in a loop, until:
[11:11:18] error Try enabling Debug mode under Settings to see a more verbose output
[11:11:18] fatal error retrieving container status: fish: Unknown command: /tmp/devpod/agent
fish:
'/tmp/devpod/agent' agent workspace status --workspace-info 'xxx'
^~~~~~~~~~~~~~~~~~^
exit status 127
Local Environment:
DevPod Provider:
Anything else we need to know?
Possible workaround before the fix: use bash as login shell.
What happened?
On a fresh copy of DevPod, I set up the SSH Provider using all default options.
I was presented with this error:
What did you expect to happen instead?
I expected DevPod to start up correctly
How can we reproduce the bug? (as minimally and precisely as possible)
From any DevPod instance, attempt to SSH to a Linux machine that has the
fish
default shellLocal Environment:
devpod version
]v0.5.4%
mac
arm64
DevPod Provider:
Anything else we need to know?