Closed misialq closed 1 year ago
@misialq thanks for creating this issue! Does this work with another provider? Also is the env variable QIIME_VERSION
set within the machine where you ssh to?
Hey @FabianKramm, I only tried with the Docker provider - also doesn't work, although there I wouldn't know where the env variable would be exactly taken from... The variable is set on the remote - I'm explicitly doing that by providing the variable through SetEnv option in the ssh config.
Hi @misialq I tried to reproduce the problem you encountered, but I didn't get any error. I'll share my steps with you to make sure we are on the same page. Please ensure you followed the following steps.
For the test purposes I forked anexample-node-app repository
and updated a .devcontainer.json
to include ${localEnv:CONTAINER}
directive.
Prepare an entry in a local .ssh/config
:
Host <my-remote-ssh-server>
SetEnv CONTAINER=mcr.microsoft.com/devcontainers/javascript-node:0-18-bullseye
Log to your remote machine and in the /etc/ssh/sshd_config
add a line:
AcceptEnv CONTAINER
Restart ssh service on your remote machine (in my case it was Debian Linux so I used the following command):
systemctl restart ssh.service
Run a devpod up
command:
devpod up --debug https://github.com/pbialon/vscode-remote-try-node --ide=none
I tried the following steps both for devpod v0.2.1 & older ssh provider v0.0.6 and for the newest version devpod v0.3.3 and ssh provider v0.0.8 and both worked.
Hi @pbialon,
many thanks for the clear instructions! I see already what went wrong for me - I forgot to add the "AcceptEnv" line... 🤦♂️ I tried it now and it all worked.
Thanks so much and sorry for polluting the issue tracker!
Happy to hear it worked for you!
I think that the process to get it working is not clear, so I'll think about adding some instruction to our documentation.
What happened? I keep getting an error when trying to create a workspace using the SSH provider. Here is the relevant section of the log:
I know that the problem is with my devcontainer.json file (see below) - I'm using an env variable to determine which Docker image should be used for the dev container. I'm also setting the respective variable in my ssh config (using the SetEnv directive), but that doesn't get picked up. Am I missing something? Is that even possible?
What did you expect to happen instead? The workspace to be created successfully.
How can we reproduce the bug? (as minimally and precisely as possible)
My
devcontainer.json
:Local Environment:
DevPod Provider:
Anything else we need to know? That's all I can think of :)