Issue for running basic pyside2 ui application at imx7D with TorizonCore OS from vs code

Technical Support
,
10

I understand you’re still experiencing the Docker registry detection issue. Let me provide additional troubleshooting approaches based on the documentation.

Alternative Registry Configuration

Since the automatic detection is failing, you can configure the registry manually. The documentation shows how to set up a local registry as a pull-through cache(1):

Create a custom config.yml file:

version: 0.1
log:
  fields:
    service: registry
storage:
  cache:
    blobdescriptor: inmemory
  filesystem:
    rootdirectory: /var/lib/registry
proxy:
  remoteurl: https://registry-1.docker.io
http:
  addr: :5000
  headers:
    X-Content-Type-Options: [nosniff]
health:
  storagedriver:
    enabled: true
    interval: 10s
    threshold: 3

(1)

Manual Registry Setup with Docker Compose

Use this docker-compose file to run the registry with proper configuration(1):

version: "3"
services:
  docker-registry:
    container_name: docker-registry
    image: registry.hub.docker.com/library/registry:2
    ports:
      - 5000:5000/tcp
    volumes:
      - ./config.yml:/etc/docker/registry/config.yml
      - ${HOME}/registry:/var/lib/registry
    restart: unless-stopped

(1)

Docker Daemon Configuration

Configure your Docker daemon to use the local registry. Create or modify /etc/docker/daemon.json in WSL(1):

{
  "registry-mirrors" : ["<host-machine-ip>:5000"]
}

(1)

ARM Emulation Re-enablement

A common issue is that ARM emulation becomes disabled. The documentation states that “Enabling Arm emulation through this method is NOT persistent. After reboots, you have to run this command again to re-enable Arm emulation”(2).

Run this command to re-enable ARM emulation(2):

$ docker run --rm -it --privileged torizon/binfmt

(2)

WSL-Specific Solutions

For WSL environments, there are specific date/time synchronization issues that can affect Docker operations(3). If you’re experiencing certificate-related errors, run this in PowerShell with admin privileges(3):

$ wsl --shutdown

(3)

Registry Port Configuration

Based on community feedback, ensure your registry is properly accessible. The community documentation suggests checking these specific configurations(4):

  1. Registry binds to 0.0.0.0 (not 127.0.0.1)
  2. Windows firewall allows the registry port
  3. Docker’s daemon.json includes your registry as insecure
  4. Only one Docker Engine instance is active (inside WSL2)

Manual Task Execution

The extension provides specific scripts for dependency management(5). You can manually execute the registry setup task:

  • Use the run-docker-registry task from the workspace tasks
  • Execute the validate-deps-running.xsh script manually to see detailed error messages

Complete Environment Reset

If all else fails, try this complete reset approach:

  1. Stop all containers: docker stop $(docker ps -aq)
  2. Remove all containers: docker rm $(docker ps -aq)
  3. Restart WSL: wsl --shutdown in PowerShell (admin)
  4. Re-enable ARM emulation: Run the binfmt command above
  5. Start fresh registry: Use the docker-compose approach
  6. Reload VS Code: Developer: Reload Window

The persistent registry detection issue in WSL environments often requires this combination of ARM emulation re-enablement and proper registry configuration rather than relying solely on the extension’s automatic setup.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.