Docker container registry is not running!

[edwaugh]

Hi,
Having previously worked this morning I cannot deploy a debug build to a device. I get the message:

VALIDATING ENVIRONMENT

❌ Docker container registry is not running!

⚠️  Please make sure to reload the VS Code Window if you had initialization errorsThe terminal process "pwsh '-nop', '.conf/validateDepsRunning.ps1'" terminated with exit code: 69.`

I tried:

• Restarting vscode
• Restarting docker
• Logging out and into docker
• Disconnecting and reconnecting the device
• Restarting my laptop

Some things I noticed:

• Container registry in docker vscode plugin was unconnected so i logged in there as well
• Plugin seems fine, powershell script runs on vscode startup and devices scan and connect ok

Workspace file includes:

"docker.environment": {
			"DOCKER_HOST": "tcp://192.168.0.110:2375",
			"DEBUG_SSH_PORT": "2222",
			"DEBUG_PORT1": "2222",
			"DEBUG_PORT2": "2223",
			"DEBUG_PORT3": "2224"
		}

Settings file is:

{
  "torizon_login": "torizon",
  "torizon_ip": "192.168.0.110",
  "torizon_ssh_port": "22",
  "host_ip": "192.168.0.108",
  "torizon_workspace": "${workspaceFolder}",
  "torizon_debug_ssh_port": "6502",
  "torizon_debug_port1": "6512",
  "torizon_debug_port2": "",
  "torizon_debug_port3": "",
  "torizon_gpu": "-imx8",
  "torizon_arch": "aarch64",
  "wait_sync": "1",
  "torizon_run_as": "root",
  "torizon_app_root": "/home/torizon/app",
  "tcb.packageName": "v3DeviceApplication",
  "tcb.version": "3.11.0",
  "torizon.gpuPrefixRC": true,
  "python.defaultInterpreterPath": "./.venv/bin/python3",
  "torizon_psswd": "********",
  "python.testing.pytestArgs": [
    "tests"
  ],
  "python.testing.cwd": "./src/",
  "python.testing.unittestEnabled": false,
  "python.testing.pytestEnabled": true
}

TDX Info

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           5.15.148-6.7.0-devel+git.bfdbfb2c85fb #1-TorizonCore SMP PREEMPT Thu Jun 20 15:59:41 UTC 2024
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.0/torizon/6a9a9ff4d30f1e447947d7c1110f900fe2552b1b3c73ac6bf5f8bf300c5facae/0
Distro name:              NAME="TorizonCore"
Distro version:           VERSION_ID=6.7.0-devel-20240917160527-build.0
Distro variant:           VARIANT="Docker"
Hostname:                 CB20300133
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Verdin iMX8M Mini on Cloudcycle Cloudbox V3
Toradex version:          0059 V1.1B
Serial number:            06899344
Processor arch:           aarch64
------------------------------------------------------------

All suggestions very welcome, I really needed to get some stuff tested this morning!

Thanks

Ed

[ToradexAI]

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

Did you like my answer?

---

Based on the context provided, it seems like the issue you’re facing is related to the Docker container registry not running, which is preventing you from deploying a debug build to your device. Here are a few suggestions to troubleshoot and potentially resolve the issue:

1. Check Docker Daemon Status: Ensure that the Docker daemon is running on your host machine. You can do this by running docker info in your terminal. If Docker is not running, start it using your system’s service manager (e.g., systemctl start docker on Linux).

2. Verify Docker Environment Variables: Double-check the environment variables in your workspace file. Ensure that the DOCKER_HOST is correctly set to the IP and port where your Docker daemon is listening. The default is usually unix:///var/run/docker.sock unless you have configured it to listen on a TCP socket.

3. Network Configuration: Ensure that there are no network issues between your host machine and the device. You can test connectivity by pinging the device’s IP address.

4. Docker Login: Since you mentioned logging in and out of Docker, ensure that your credentials are correct and that you have access to the necessary container registries.

5. VS Code Extension: Since the error message suggests reloading the VS Code window, try doing so after ensuring that Docker is running. You can reload the window by pressing Ctrl+Shift+P and selecting “Reload Window”.

6. Check for Errors in Logs: Look at the Docker logs for any errors that might indicate why the registry is not running. You can view logs using docker logs <container_id> if you have a specific container in mind.

7. PowerShell Script: The error message references a PowerShell script (validateDepsRunning.ps1). Check this script for any specific checks or conditions that might be failing and causing the error.

If none of these steps resolve the issue, it might be helpful to consult the Docker documentation or reach out to Toradex support for more specific guidance related to your setup.

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

Local Docker Registry stops working after runing torizoncore-builder

Hi, I have set up a local docker register to use in conjuction with torizoncore-builder (tcb from here onwards). I am running in WSL2 with a Windows 10 host. The local register works fine and I can push/pull stuff to it without issue. ~/tcbworkdir/dockers/custom_weston> docker build -t localhost:5000/custom_weston . ~/tcbworkdir/dockers/custom_weston> docker push localhost:5000/custom_weston Using default tag: latest The push refers to repository [localhost:5000/custom_weston] c910081…

Error doing debug and deploy build on VS for getting started

Greetings, Going through getting started procedure and am at point where creating a project, debug and deploy. First a discrepency: The getting started text says make sure to select “debian buster-slim arm32v7” but the image shows “debian buster-slim arm64v8-1.0”. The referenced Visual Studio Extension document says select the option “debian buster_slim:arm64v8 - 1.0:” for Apalis iMX8QM. I’ve tried both… When I click Deploy and debug torizon Application it opens the “Application is not up to d…

Problems setting up VS Code IDE Extension V2.

[henrique.tx]

Hi @edwaugh !

Which OS are you using on your computer? Is this Windows?

Could you please share the output of the following commands:

docker ps -a
systemctl status docker
systemctl status docker.socket

Be sure to execute these commands in your host’s terminal. You can use VS Code’s terminal or from WSL’s.

Best regards,

[edwaugh]

Hi @henrique.tx I hope you are well.

Docker ps very slow to respond:

Get "http://192.168.0.108:2375/v1.47/containers/json?all=1": dial tcp 192.168.0.108:2375: i/o timeout

Next two look quite fatal:

System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

Doing ipconfig on Windows:

Wireless LAN adapter WiFi:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::86a5:eb75:c03:c00c%6
   IPv4 Address. . . . . . . . . . . : 192.168.0.108
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1

Ethernet adapter vEthernet (WSL (Hyper-V firewall)):

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::54c0:cc48:d31c:c1fa%83
   IPv4 Address. . . . . . . . . . . : 172.28.64.1
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . :

Thanks

Ed

[drew.tx]

Hi Ed,

The message about “systemd as init system” is normal when running Ubuntu or some other desktop container image since they will not normally have an init system and just run the containers entrypoint instead.

Can you describe how this system was set up? Did you do it recently or some time ago? I know our dev team reworked the Windows installation to make it just a couple of clicks for you as it can be tricky to get all the parts installed in the right places. Basically, you install VSCode native in windows but then extensions are used to connect into WSL and do all the work transparently from there. If this machine has been setup for some time, or actually setup with the first version of the IDE extension, you may want to clean everything (VSCode, docker, etc) off the system and start fresh with the new WSL install method. More details are in this blog post and this developer page.

HTH,

Drew

[edwaugh]

Hi Drew,
I set it up about 3 weeks ago using the script that configures everything for you. It worked ok initially. Since then I have used the torizon container to clone another repo and build a .so file from C which required apt installing a couple of libraries. Nothing that I think could have upset it.

I can go back to the start and try reinstalling it all again maybe.

Thanks

Ed

[edwaugh]

Ok so docker desktop had an update pending, I did that, restarted vscode and now it seems to be working. Not sure what happened there!

[drew.tx]

That still counts as a win; I’ll take it.

Let us know if you have any other issues.

Drew