VScode remote not using the same path as vscode locally

Question

I've been working on some Jupyter notebooks in VSCode. Jupyter isn't very git friendly, so when I want to commit my notebooks to Git, I have a filter that scrubs the output by using jupyter nbconvert --ClearOutputPreprocessor.enabled=True --to=notebook --stdin --stdout.

This works fine locally with git commits in VSCode in the source control view (⌃⇧G).

However when I connect to the same machine remotely via VSCode, I get errors that jupyter nbconvert --ClearOutputPreprocessor.enabled=True --to=notebook --stdin --stdout --log-level=ERROR: 1: jupyter: not found.
Jupyter is in my $PATH and works locally. It also works when I use the terminal window in a remote VSCode session. It only fails in the remote source control view. Any ideas?

score 1 · Answer 1 · edited Feb 01 '22 at 08:00

1

It depends on where you defined your PATH: .profile or .bashrc.

"alter PATH for VS Code Remote SSH" mentions I modified the path in ~/.bashrc and it worked.
"Set global $PATH environment variable in VS Code" suggests:

Ctrl + Shift + P and then type Open Settings (JSON), and simply add the following line.
"terminal.integrated.inheritEnv": true

edited Feb 01 '22 at 08:00

LeGEC

46,477
5
57
104

answered Feb 01 '22 at 08:00

VonC

1,262,500
529
4,410
5,250

@LeGEC merci beaucoup – VonC Feb 01 '22 at 08:01
That line was already there in my settings – pgcudahy Feb 21 '22 at 17:15
@pgcudahy OK. And would the first point help? (the one about `~/.bashrc` path) – VonC Feb 21 '22 at 17:54

VScode remote not using the same path as vscode locally

1 Answers1