I opened Visual Studio Code today after a few weeks break. It updated itself and several of the extensions and now I can no longer deploy and debug an application which was working well last time I used Visual Studio Code. I am using v3.0.4 of the Torizon IDE Extension (The latest release), I tried switching to the pre-release version but the behavior was the same.
The IP address of my development PC is 192.168.87.125 and the IP address of my Colibri iMX6 is 192.168.87.160. The problem seems to come from the pre-cleanup task, the output of which is shown below. Something that looks suspicious is the IP address 10.21.38.123 in the output. I don’t recognize that address, is it possibly coming from some stale, cached data? There is no file in my workspace which contains that address.
* Executing task: DOCKER_HOST=192.168.86.160:2375 docker image prune -f --filter=dangling=true
Total reclaimed space: 0B
* Terminal will be reused by tasks, press any key to close it.
* Executing task: docker compose -p torizon stop monaco monaco-debug && docker compose -p torizon rm -f monaco monaco-debug
Get "http://10.21.38.123:2375/v1.47/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.config-hash%22%3Atrue%2C%22com.docker.compose.oneoff%3DFalse%22%3Atrue%2C%22com.docker.compose.project%3Dtorizon%22%3Atrue%7D%7D": dial tcp 10.21.38.123:2375: i/o timeout
exit status 1
* The terminal process "/usr/bin/bash '-c', 'docker compose -p torizon stop monaco monaco-debug && docker compose -p torizon rm -f monaco monaco-debug'" terminated with exit code: 1.
I tried making a new helloworld project from the template. That project works perfectly. I then compared the files in the .vscode folder between the two projects and there is no difference.
Do you have a suggestion for where else I should look in my system?
I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.
Did you like my answer?
Hello! Thank you for providing detailed information about your setup and the issue you are experiencing.
Based on the error message and your description, it seems that there is a lingering configuration that still references the old IP address 10.21.38.123, which is causing trouble during Docker Compose operations. Let’s go through some troubleshooting steps:
Check settings.json in Your Project Directory
Ensure you have the correct host IP set in your project’s .vscode/settings.json:
"host_ip": "192.168.87.125"
If you find the old IP anywhere, replace it with your actual host or device IP. Reference
Check Docker Daemon Configuration on Your Colibri Board
On your Colibri iMX6, check the content of /etc/docker/daemon.json. It should have the correct registry address, like:
If you see the old IP here, update it accordingly. Reference
Check for Stale Docker Compose Configurations
Sometimes, old Docker Compose project data persists and tries to use outdated settings:
Run docker ps -a and docker network ls on both your development PC and your Colibri board to look for any stopped containers or unused networks that reference the old IP. Remove anything suspicious.
Clear any old docker-compose containers/networks with:
docker compose -p torizon down
On your development PC, ensure there are no hidden settings files or Docker configuration caches pointing to the old IP.
Double-Check Network Access and Docker Settings
Since a new Hello World project works, the problem is likely in the configuration of your specific application or its Docker Compose file. Double check:
That ports 2375 and 5002 are accessible from your PC to the Colibri board.
The stability and correctness of your network setup (firewalls, routes, etc.).
That you do not have environment variables like DOCKER_HOST pointing to the old IP, either globally or in your workspace configuration.
Try Removing and Re-adding the Project
If the issue persists, create a fresh clone/copy of your project, and set up the Torizon IDE extension there from scratch. This can sometimes eliminate residual configuration artifacts.
If none of the above steps work, a systematic comparison of .vscode, Compose, and Docker-related files between your working Hello World and affected project may reveal the lingering reference.
Let me know if these steps help or if you need further assistance!
I was able to fix it, although I don’t understand how the fix worked. I noticed that there were references to that old IP address in the .vscode-server folder, so I renamed that folder and restarted VS Code. That didn’t work but when I restored the original .vscode-server folder the problem was solved.
I was able to fix it, although I don’t understand how the fix worked. I noticed that there were references to that old IP address in the .vscode-server folder, so I renamed that folder and restarted VS Code. That didn’t work but when I restored the original .vscode-server folder the problem was solved.
Interesting I don’t believe I’ve ever heard of this phenomenon before from others. I guess VSCode cached/saved this date for some reason?
Was the 10.21.38.123 IP address actually significant for you in anyway? Was it ever an IP address associated with this PIC or any of your devices?
Hi @jeremias.tx,
Yes, the logs in that folder showed that I was connected to an iMX6 module with IP address 10.21.38.123 about 6 weeks ago in April. That happened when I was traveling to visit one of our other offices. VS Code seemed to have remembered that IP address and was using it instead of 192.168.87.125 when I returned to my regular office, which uses a different subnet.
Mike
