You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(I tried to find if someone already answered my question, but the only "well fitting" issue was closed (without solution).)
I want to connect to a Jetson (Xavier) running the jetson-inference docker container. I want to use VS Code for it.
So my username on my local Linux machine differs to the one on the Jetson. I created an ssh key and copied it to the machine. Means when I connect via ssh to the Jetson I am logging in as their local user ("xavier-nx") without having a password prompt. I tried to connect to the docker container without the ssh key stuff before (so typed in the password etc) without success.
When I am now connected I try to attach to the running container. VS Code asks me what container to use - I select the only available one.
VS Code then tries to connect but fails.
Within the VS-Code logs I see these lines:
[7951 ms]
[7951 ms]
[7951 ms] Exit code 127
[7952 ms] Start: Run in container: /bin/sh
[7952 ms] userEnvProbe: loginInteractiveShell (default)
[7952 ms] Start: Run in container: test -f '/tmp/devcontainers-291ca786-a236-4b2c-9e47-22e9e07c610d1740561987510/env-loginInteractiveShell.json'
[7958 ms] Error: EACCES: permission denied, open '/home/ronny/.ssh/known_hosts'
[7958 ms] Exit code EACCES
It tried to access my local Linux computers username.
It does not matter if I set a remoteUser or containerUser in the "devcontainer.json".
So: what is the "proper" way to develop remotely on the Jetson's docker containers (means also executing the eg. python scripts from within VS code so that I can see the results on my local computer - like I am able when running things "non-containerized" on the Jetson plus normal remote-development)?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
When connecting via authorized_keys (so "/home/myusername/.ssh/xyz-xaviernx.pub"-content pasted into xavier-nx's file system "/home/xavier-nx-username/.ssh/authorized_keys") then you can connect to the xavier-nx without password prompt.
Next step would be the connection to the docker-container. This one fails because of some eaccess error (and by default docker-buildx is not installed on the xavier with a fresh Jetpack-SD-Card-Install).
After installing docker-buildx on the xavier host the error about it being missing is gone but the eaccess one still was there.
So I brought in my xavier-nx-user's .ssh into docker - but in this case it was required to store it in the (not existing previously) home directory of the remote-user!
Means: on the xavier I am using the username "xavier-nx", on my development computer I use "ronny".
would mount the ssh authorized keys etc of "xavier-nx" into the docker container for the remote user "ronny".
While this seemed to fix the issue, The next error was about known_hosts ... so ssh surely blamed the not knowing the host.
While the docker container was running I simply did a touch /home/ronny/.ssh/known_hosts (so indirectly creating that file on the xavier's directory /home/xavier-nx/.ssh/known_hosts).
After this I was able to attach to the docker container from my local development computer.
It just needed to install the python-extension in vs code and I was able to execute the jetson-inference-samples:
Heya,
(I tried to find if someone already answered my question, but the only "well fitting" issue was closed (without solution).)
I want to connect to a Jetson (Xavier) running the jetson-inference docker container. I want to use VS Code for it.
So my username on my local Linux machine differs to the one on the Jetson. I created an ssh key and copied it to the machine. Means when I connect via ssh to the Jetson I am logging in as their local user ("xavier-nx") without having a password prompt. I tried to connect to the docker container without the ssh key stuff before (so typed in the password etc) without success.
When I am now connected I try to attach to the running container. VS Code asks me what container to use - I select the only available one.
VS Code then tries to connect but fails.
Within the VS-Code logs I see these lines:
It tried to access my local Linux computers username.
It does not matter if I set a remoteUser or containerUser in the "devcontainer.json".
So: what is the "proper" way to develop remotely on the Jetson's docker containers (means also executing the eg. python scripts from within VS code so that I can see the results on my local computer - like I am able when running things "non-containerized" on the Jetson plus normal remote-development)?
Thanks in advance.
The text was updated successfully, but these errors were encountered: