This tool came to life after observing new customers do the setup manually in training sessions and customer calls. And, to close the feedback cycle and further increase your user experience, we look forward to feedback on the first implementation, available in Early Access.
How would you rate the new experience setting up a Windows machine for Torizon development?
An issue was found with the Docker initialization configuration on the Torizon Development Environment for WSL. Unfortunately, is not possible to update without uninstall the old version and install it again. To uninstall it run the follow command from the VS Code pallet (Windows side):
After run the command, please go through the Torizon IDE Installation Wizard again.
This helps to set expectations and remember that this feature is still experimental. And always remember that your feedback is very important to us, so don’t be shy about leaving anything, bad or good, about the feature here.
I’m having some trouble installing the Torizon IDE extension in Visual Studio code for Windows and was hoping someone here might be able to help.
I followed the steps from a video I found online, but unfortunately, it’s not working as expected. I’ve made sure that my Visual Studio code is up to date, and I’ve tried reinstalling the extension a couple of times with no success.
Here’s a brief overview of what I did:
1.Downloaded the Visual Studios code and installed the Torizon IDE extension.
2. After the system verification tick box is selected then for installing WSL it restarts after that if I tried to install again it starts from system verification tick box and the cycle repeats.
Has anyone else faced this issue or has any insights on what might be going wrong? Are there any additional steps or troubleshooting tips that I might have missed?
Any help or suggestions would be greatly appreciated!
so, it seems that the wizard was not able to enable the WSL 2 on your system. Could you share the version of your Windows installation and the hardware that you have?
I am having trouble with the Torizon IDE installation Wizard too.
After clean install, it goes through System Verification, WSL Installed, Torizon WSL2 Installed, but runs into error on Configure Torizon on WSL2.
What I see is a popup window that disappears quickly.
I think this is supposed to be a Welcome screen with username and password fields.
I can see that the WSL Torizon distribution is created via “wsl --list”.
When launching the Torizon WSL directly, I see this error
wsl
Welcome to the Torizon WSL 2 v0.0.18
Stack overflow.
at SlintDotnet.SlintDotnet._FnRun()
at SlintDotnet.SlintDotnet.Run()
at AppWindow.Window.Run()
at Program.$(System.String)
Error: User not added?
Bye!
Hi @matheus.tx
I’ve already been using Ubuntu-22.04 in WSL2 with Torizon Extension since months, but now I’ve just tried this wizard to install Torizon for WSL2 as a linux distribution.
I followed the video here.
Everything is ok with the installation, and I can see mi Torizon SoMs connected.
Good!
Then I created the same Python 3 Console project as in the video.
I tried to debug it, but I can’t because of the following error:
* Executing task: pwsh -nop /home/vix/test/.conf/torizonPackages.ps1 aarch64
Applying torizonPackages.json ...
Applying to Dockerfile.debug ...
âś… Dockerfile.debug
Applying to Dockerfile ...
âś… Dockerfile
torizonPackages.json applied
* Terminal will be reused by tasks, press any key to close it.
* Executing task: DOCKER_HOST= docker compose --ansi never build --pull --build-arg SSHUSERNAME=torizon --build-arg APP_ROOT=/home/torizon/app --build-arg IMAGE_ARCH=arm64 --build-arg DEBUG_SSH_PORT=6502 --build-arg GPU=-imx8 test-debug
WARN[0000] The "DOCKER_LOGIN" variable is not set. Defaulting to a blank string.
WARN[0000] /home/vix/test/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
#0 building with "default" instance using docker driver
#1 [test-debug internal] load build definition from Dockerfile.debug
#1 transferring dockerfile: 2.81kB done
#1 DONE 0.0s
#2 [test-debug internal] load metadata for docker.io/commontorizon/debian:3.3.1-bookworm
#2 DONE 4.8s
#3 [test-debug internal] load .dockerignore
#3 transferring context: 117B done
#3 DONE 0.0s
#4 [test-debug 1/8] FROM docker.io/commontorizon/debian:3.3.1-bookworm@sha256:d62ff0a4cc79fc27ea436ccbe38b8eeec1b2944d9114a923e58496676112720d
#4 DONE 0.0s
#5 [test-debug internal] load build context
#5 transferring context: 43B done
#5 DONE 0.0s
#6 [test-debug 7/8] RUN mkdir /var/run/sshd && sed 's@session\s*required\s*pam_loginuid.so@session optional pam_loginuid.so@g' -i /etc/pam.d/sshd && if test torizon != root ; then mkdir -p /home/torizon/.ssh ; else mkdir -p /root/.ssh ; fi && echo "PermitUserEnvironment yes" >> /etc/ssh/sshd_config && echo "PermitRootLogin yes" >> /etc/ssh/sshd_config && echo "Port 6502" >> /etc/ssh/sshd_config && echo "PasswordAuthentication yes" >> /etc/ssh/sshd_config && echo "PermitEmptyPasswords yes" >> /etc/ssh/sshd_config && su -c "env" torizon > /etc/environment && echo "torizon:" | chpasswd -e
#6 CACHED
#7 [test-debug 3/8] RUN apt-get -q -y update && apt-get -q -y install && apt-get clean && apt-get autoremove && rm -rf /var/lib/apt/lists/*
#7 CACHED
#8 [test-debug 6/8] RUN . /home/torizon/app/.venv/bin/activate && pip3 install --upgrade pip && pip3 install -r requirements-debug.txt && rm requirements-debug.txt && chown -R torizon:torizon /home/torizon/app
#8 CACHED
#9 [test-debug 2/8] RUN apt-get -q -y update && apt-get -q -y install openssl openssh-server rsync file screen python3-minimal python3-pip python3-setuptools python3-venv && apt-get clean && apt-get autoremove && rm -rf /var/lib/apt/lists/*
#9 CACHED
#10 [test-debug 4/8] RUN python3 -m venv /home/torizon/app/.venv --system-site-packages
#10 CACHED
#11 [test-debug 5/8] COPY requirements-debug.txt /requirements-debug.txt
#11 CACHED
#12 [test-debug 8/8] RUN rm -r /etc/ssh/ssh*key && dpkg-reconfigure openssh-server
#12 CACHED
#13 [test-debug] exporting to image
#13 exporting layers done
#13 writing image sha256:05a7ecb5363fa11fd281d07a0f31f0a94f2dcf662d691c9ec1e90cd3d9d14748 done
#13 naming to localhost:5002/test-debug:arm64 done
#13 DONE 0.0s
#14 [test-debug] resolving provenance for metadata file
#14 DONE 0.0s
* Terminal will be reused by tasks, press any key to close it.
* Executing task: DOCKER_HOST= docker compose --ansi never push test-debug
WARN[0000] The "DOCKER_LOGIN" variable is not set. Defaulting to a blank string.
WARN[0000] /home/vix/test/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
Pushing localhost:5002/test-debug:arm64: 6b6184be22d2 Preparing
Pushing localhost:5002/test-debug:arm64: f7cbadd5a280 Preparing
Pushing localhost:5002/test-debug:arm64: 41dc7bdcb7be Preparing
Pushing localhost:5002/test-debug:arm64: 819ebf64c20f Preparing
Pushing localhost:5002/test-debug:arm64: 929377a53df4 Preparing
Pushing localhost:5002/test-debug:arm64: 59b3ae74375f Preparing
Pushing localhost:5002/test-debug:arm64: cc2d578af58b Preparing
Pushing localhost:5002/test-debug:arm64: bb95280742bd Preparing
Pushing localhost:5002/test-debug:arm64: d5661228a6f6 Preparing
Pushing localhost:5002/test-debug:arm64: 1f74cca9ef3c Preparing
Pushing localhost:5002/test-debug:arm64: cf08845a6a01 Preparing
Pushing localhost:5002/test-debug:arm64: e009595c7dc0 Preparing
Pushing localhost:5002/test-debug:arm64: 6dc89911362e Preparing
Pushing localhost:5002/test-debug:arm64: 0d7dccc6d0e7 Preparing
Pushing localhost:5002/test-debug:arm64: 67ca54a26679 Preparing
Pushing localhost:5002/test-debug:arm64: 3440d23a444f Preparing
Pushing localhost:5002/test-debug:arm64: 5a49bdb65752 Preparing
Pushing localhost:5002/test-debug:arm64: 2bd1a2222589 Preparing
Pushing localhost:5002/test-debug:arm64: 6dc89911362e Waiting
Pushing localhost:5002/test-debug:arm64: 0d7dccc6d0e7 Waiting
Pushing localhost:5002/test-debug:arm64: 67ca54a26679 Waiting
Pushing localhost:5002/test-debug:arm64: cc2d578af58b Waiting
Pushing localhost:5002/test-debug:arm64: bb95280742bd Waiting
Pushing localhost:5002/test-debug:arm64: 3440d23a444f Waiting
Pushing localhost:5002/test-debug:arm64: d5661228a6f6 Waiting
Pushing localhost:5002/test-debug:arm64: 1f74cca9ef3c Waiting
Pushing localhost:5002/test-debug:arm64: 5a49bdb65752 Waiting
Pushing localhost:5002/test-debug:arm64: cf08845a6a01 Waiting
Pushing localhost:5002/test-debug:arm64: e009595c7dc0 Waiting
Pushing localhost:5002/test-debug:arm64: 2bd1a2222589 Waiting
Pushing localhost:5002/test-debug:arm64: 59b3ae74375f Waiting
Pushing localhost:5002/test-debug:arm64: 6b6184be22d2 Layer already exists
Pushing localhost:5002/test-debug:arm64: f7cbadd5a280 Layer already exists
Pushing localhost:5002/test-debug:arm64: 41dc7bdcb7be Layer already exists
Pushing localhost:5002/test-debug:arm64: 929377a53df4 Layer already exists
Pushing localhost:5002/test-debug:arm64: 819ebf64c20f Layer already exists
Pushing localhost:5002/test-debug:arm64: 59b3ae74375f Layer already exists
Pushing localhost:5002/test-debug:arm64: cc2d578af58b Layer already exists
Pushing localhost:5002/test-debug:arm64: bb95280742bd Layer already exists
Pushing localhost:5002/test-debug:arm64: d5661228a6f6 Layer already exists
Pushing localhost:5002/test-debug:arm64: 1f74cca9ef3c Layer already exists
Pushing localhost:5002/test-debug:arm64: cf08845a6a01 Layer already exists
Pushing localhost:5002/test-debug:arm64: 6dc89911362e Layer already exists
Pushing localhost:5002/test-debug:arm64: e009595c7dc0 Layer already exists
Pushing localhost:5002/test-debug:arm64: 67ca54a26679 Layer already exists
Pushing localhost:5002/test-debug:arm64: 0d7dccc6d0e7 Layer already exists
Pushing localhost:5002/test-debug:arm64: 3440d23a444f Layer already exists
Pushing localhost:5002/test-debug:arm64: 5a49bdb65752 Layer already exists
Pushing localhost:5002/test-debug:arm64: 2bd1a2222589 Layer already exists
* Terminal will be reused by tasks, press any key to close it.
* Executing task: DOCKER_HOST=192.168.137.129:2375 LOCAL_REGISTRY=10.10.10.17 TAG=arm64 GPU=-imx8 DEBUG_SSH_PORT=6502 DEBUG_PORT1=6512 DEBUG_PORT2= DEBUG_PORT3= docker compose --ansi never pull test-debug
WARN[0000] The "DOCKER_LOGIN" variable is not set. Defaulting to a blank string.
WARN[0000] /home/vix/test/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
test-debug Pulling
test-debug Warning Get "http://10.10.10.17:5002/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
WARNING: Some service image(s) must be built from source by running:
docker compose build test-debug
1 error occurred:
* Error response from daemon: Get "http://10.10.10.17:5002/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
* The terminal process "/bin/bash '-c', 'DOCKER_HOST=192.168.137.129:2375 LOCAL_REGISTRY=10.10.10.17 TAG=arm64 GPU=-imx8 DEBUG_SSH_PORT=6502 DEBUG_PORT1=6512 DEBUG_PORT2= DEBUG_PORT3= docker compose --ansi never pull test-debug'" terminated with exit code: 18.
* Terminal will be reused by tasks, press any key to close it.
this sounds like some issue with your local network configuration. I do not know if you are using some VPN, but probably the extension automatically host IP detection is not getting the right one. Check if the 10.10.10.17 is the right IP, if not, set the follow configuration in your VS Code global settings.json:
"torizon.overwriteHostIp": "192.168.0.6"
Where you should change the 192.168.0.6 with your main interface IP address.
if on Windows you’re logged with an user without administrative rights, the Wizard doesn’t work because it asks you the administrator password to install WSL (step 2), then it reboots. But then it asks again to install WSL, it asks for administrator password, it reboots and so on.
you must open a terminal for the user logged to windows, and run wsl --update from there
then the step 2 passes
the torizon VM has a user named castello inside the /home folder
I have carried out the integration of Torizon IDE Extension step by step using the video. After clicking the CONNECT TO WSL 2 button, I am connected to WSL:Torizon. However, the Torizon IDE Extension is not installed here.
Without logs is hard to say. Could you uninstall the WSL Torizon development for WSL 2 and try again? But, before click on CONNECT TO WSL 2 check the output panel for the logs, then share it here.
An issue was found with the Docker initialization configuration on the Torizon Development Environment for WSL. Unfortunately, is not possible to update without uninstall the old version and install it again. To uninstall it run the follow command from the VS Code pallet (Windows side):
ERROR
