Today, I have a new version of VSC. Here is my issue when I try to debug.
Executing task: /home/steve/Gmbal3/.conf/remove-dangling-images.xsh 10.40.100.5:2375
execvp(3) failed.: Permission denied
What now? I can ssh into my device, no issues.
Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
To help troubleshoot your VSCode debugging issue with the Torizon IDE Extension, I need to understand your setup better. Could you let me know:
- Which OS and version are you running on your device?
- What type of SoM and carrier board are you using?
You can get this information by running the tdx-info command on your device. More details about this command can be found at Getting Device Information with Tdx-Info | Toradex Developer Center
The “execvp(3) failed.: Permission denied” error when executing the remove-dangling-images.xsh script suggests a permissions issue with the Docker daemon or the script execution environment (1). This is different from SSH connectivity, which you’ve confirmed is working.
Once I know your specific platform and OS version, I can provide more targeted guidance for resolving this debugging issue with the Torizon IDE Extension.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
Software summary
Bootloader: U-Boot
Kernel version: 6.6.94-7.3.0-g5a62539de8f9 #1-Torizon SMP PREEMPT Wed Jun 25 09:14:55 UTC 2025
Kernel command line: root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/5c84b03643fe3e8b7be49b13c2171a7f45d0dce855097b9fafed3f75e9260a47/0
Distro name: NAME=“Torizon OS”
Distro version: VERSION_ID=7.3.0-build.18
Distro variant: VARIANT=“Docker”
Hostname: verdin-imx8mp-15132679
Hardware info
HW model: Toradex Verdin iMX8M Plus WB on Verdin Development Board
Toradex version: 0058 V1.1A
Serial number: 15132679
Processor arch: aarch64
It isn’t really the Verdin Dev board, but very similar.
Thanks for providing the system information! I can see you’re running Torizon OS 7.3.0-build.18 on a Verdin iMX8M Plus WB with a custom carrier board.
Troubleshooting the Permission Denied Error
The “execvp(3) failed.: Permission denied” error when running the remove-dangling-images.xsh script is likely related to Docker daemon permissions or script execution rights(1). Here are several steps to resolve this:
1. Check Docker Daemon Access
Verify that Docker is running and accessible on your target device:
docker info
2. Verify Script Permissions
The .xsh scripts in the .conf directory need proper execution permissions(1). On your development machine, check:
ls -la .conf/remove-dangling-images.xsh
chmod +x .conf/remove-dangling-images.xsh
3. Docker Group Membership
Similar to the issue described in the community forums(2), ensure your user has proper Docker permissions. On your development machine, verify you’re in the docker group:
sudo usermod -aG docker $USER
Then log out and back in for the changes to take effect.
4. WSL2 Considerations (if applicable)
If you’re using WSL2, there might be additional permission considerations with the Docker daemon access(1).
5. Alternative Debugging Approach
As a workaround, you can try running the debug task manually to isolate the issue:
- Check if other Torizon IDE Extension tasks work properly
- Try building the container first before debugging
- Verify the Docker registry connectivity to your target device
The script remove-dangling-images.xsh is part of the Torizon IDE Extension’s cleanup process(1), so this permission issue is preventing proper container management during the debug workflow.
Best regards, Toradex AI Assistant.
Did you like my answer?
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
So, the “chmod +x .conf/remove-dangling-images.xsh” solved that issue. Now I am back to where I was yesterday. It can’t seem to reach the registry, even though I can run the curl command :
curl --max-time 5 http://localhost:5002/v2/_catalog
from the commandline and it works fine.
@ToradexAI
This seems to be the error that is causing the issue:
Container Runtime: docker
Run Arguments: --rm -d --network host torizonextras/ide-port-tunnel:0.0.0 sshpass -p torizon ssh -vv -N -R 5002:localhost:5002 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o PubkeyAuthentication=no torizon@10.40.100.5
Container Name: torizon-ide-port-tunnel
Container does not exist. Starting …
Cmd: docker run --name torizon-ide-port-tunnel --rm -d --network host torizonextras/ide-port-tunnel:0.0.0 sshpass -p torizon ssh -vv -N -R 5002:localhost:5002 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o PubkeyAuthentication=no torizon@10.40.100.5
Unable to find image ‘torizonextras/ide-port-tunnel:0.0.0’ locally
0.0.0: Pulling from torizonextras/ide-port-tunnel
589002ba0eae: Already exists
56bd978b24f4: Pull complete
Digest: sha256:e8d978c2f15c7797fa5ea0b3f5b4c09fdf7e4c87ff22d9f972e3493afd0a9661
Status: Downloaded newer image for torizonextras/ide-port-tunnel:0.0.0
WARNING: image with reference torizonextras/ide-port-tunnel:0.0.0 was found but its platform (linux/amd64) does not match the specified platform (linux/arm64)
docker: Error response from daemon: image with reference torizonextras/ide-port-tunnel:0.0.0 was found but its platform (linux/amd64) does not match the specified platform (linux/arm64)
Hi @EvetsMostel1!
We always recommend opening different threads for different issues. This way, we can organize and prioritize the support queue.
That said, I’ll kindly ask you to start a new thread with the other issue and leave this one as solved.
Best regards.