TorizonCore Builder on Azure VM results in ConnectionRefusedError

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

The issue you’re experiencing with the ConnectionRefusedError when using the bundle command in TorizonCore Builder on an Azure VM seems to be intermittent and might be related to network or resource availability issues on the VM. Here are a few suggestions to help diagnose and potentially resolve the issue:

1. Resource Availability: Ensure that your Azure VM has sufficient resources (CPU, memory, and disk space) to handle the operations being performed by TorizonCore Builder. Sometimes, resource constraints can lead to intermittent failures.

2. Network Stability: Check the network stability and connectivity of your Azure VM. Intermittent network issues can cause connection errors when the tool tries to communicate with Docker or other services.

3. Docker Daemon: Verify that the Docker daemon is running properly on your VM. You can restart the Docker service to ensure it’s in a good state before running the TorizonCore Builder commands.

4. Docker-in-Docker (DinD) Configuration: Since TorizonCore Builder uses Docker-in-Docker, ensure that the DinD setup is correctly configured and that there are no conflicts with other Docker services running on the VM.

5. Logs and Debugging: Continue capturing debug logs when the issue occurs. Look for any patterns or specific conditions that might trigger the error. This information can be valuable for further troubleshooting.

6. Retry Logic: As a temporary workaround, consider implementing a retry mechanism in your build pipeline. If the bundle command fails due to a connection error, automatically retry the command after a short delay.

7. Contact Support: If the issue persists and you have captured detailed logs, consider reaching out to Toradex support with the logs and a description of the problem. They might be able to provide more specific guidance or identify any known issues.

These steps should help you narrow down the cause of the intermittent ConnectionRefusedError and improve the reliability of your build pipeline on the Azure VM.

Please, also check if these links can help you solve your problem:

TorizonCore-Builder Bundle

I successfully created and pushed (docker push) an image onto a docker registry using VS Code, In my WSL working directory and can successfully pull the image (docker pull). I placed a docker-compose.yml file in my WSL working directory. When I issue the TorizonCore-Builder bundle command I receive the response “Can’t retrieve container information from docker”. I’m not sure why i get this. I 'm also not certain about which docker-compose.yml file should be used. In my VS Code project director…

Run Docker Desktop for Windows in a VM or VDI environment

Issues with private docker registries using torizoncore-builder 3.7.0+early-access.