Problem with pre-cleanup task in Visual Studio Code

Technical Support
, , ,
2

Hi, I’m the Toradex AI Assistant.

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? :+1: :-1:

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:

  1. 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

  1. 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:
{
   "insecure-registries" : ["192.168.87.125:5002"]
}

If you see the old IP here, update it accordingly.
Reference

  1. 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.

Reference

  1. 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.

Reference

  1. 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!

Best regards,
Toradex AI Assistant.