Hi ,
Thanks for reaching out to Microsoft Q&A.
Yes, your almost right. This is not an Akri or DevX runtime issue; it is a Kubernetes DNS and outbound connectivity issue on the node running the devx-runtime container.
What is happening is simple. The devx-runtime spins up a lightweight Kubernetes cluster and tries to pull a required image (mqbuilds.azurecr.io/common-operator:1.3.0). The pull fails because the node cannot resolve mqbuilds.azurecr.io, which means DNS resolution from inside the Kubernetes environment is broken or outbound HTTPS access is blocked. This typically happens when CoreDNS is not functioning correctly, the host machine has restrictive corporate proxy or firewall rules, or Docker Desktop/WSL2 networking is misconfigured.
The fix is equally straightforward but non-negotiable:
ensure the Kubernetes node can resolve public DNS and reach Azure Container Registry over HTTPS. Verify CoreDNS is running and healthy, confirm /etc/resolv.conf inside the node points to a working DNS server, and if you are behind a proxy, configure Docker, Kubernetes, and the devx-runtime to use that proxy explicitly. Without outbound DNS and HTTPS access, the Akri debug flow will never work.
Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.