Unfortunately, when fundamental changes are made like suddenly break being able to pull an image from hub with errors like “connect: network is unreachable” and no internet searchable answers either google or Docker forums, I cannot make a valid justification for not jumping to Azure.
Especially when other teams are able to maintain productivity with Azure, yet I cannot.
it’s a drag
Some company networks require http proxies, others might force tls inspection, or are even air gapped. None of those can be automatically fixed by docker. But the first two can be tackled by configuring your docker engine properly. You should talk to your companies it support about the issue, as they should know how network traffic is handled and should be able to tell you how docker needs to be configured.
I am not sure if I am able to follow your thought… Docker is a container runtime. Azure is a Cloud Hyperscaller.
“network is unreachable” is hardly a Docker Hub issue and since you haven’t shared what kind of Docker you are using on what platform, and how you installed it, it is hard to tell what the problem could be. There are multiple variants of Docker and different errors could occur on each operating system also depending on the chosen backend (like hyperv and wsl2 on Windows).
We also don’t know whether it ever worked for you. Or if it worked in other environments or what version you used.
You also mention “searchable answers” but a title like “Docker used to be cool” will not help other users either (I’m going to change the title). And it will not help you to get more replies when it doesn’t indicate network issue or any issue at all.
If you share more info someone might be able to help. Until that (and possibly even after), @meyay’s answer is the best.
Negative, good friend. Routing isn’t a problem.
wget registry-1.docker.io
–2025-01-30 11:19:38-- http://registry-1.docker.io/
Resolving registry-1.docker.io (registry-1.docker.io)… 3.94.224.37, 44.208.254.194, 98.85.153.80, …
Connecting to registry-1.docker.io (registry-1.docker.io)|3.94.224.37|:80… connected.
HTTP request sent, awaiting response… 301 Moved Permanently
Location: https://registry-1.docker.io/ [following]
–2025-01-30 11:19:38-- https://registry-1.docker.io/
Connecting to registry-1.docker.io (registry-1.docker.io)|3.94.224.37|:443… connected.
HTTP request sent, awaiting response… 404 Not Found
2025-01-30 11:19:38 ERROR 404: Not Found.
I believe this is a permissions issue, I have built docker servers in the past with “…network unreachable” errors that have turned out to be permissions issue. The problem is I cannot find decent troubleshooting docs to help peel the onion.
Username (xxxxxxxxxx):
Password:
error during connect: This error may indicate that the docker daemon is not running.: Post “http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/auth”: open //./pipe/docker_engine: The system cannot find the file specified.
The uri in the last error message looks like a very old Docker Desktop for Windows version… You might want to update it to the latest Docker Desktop version (=i4.38.0).
The wget
request shows an expected result. If I query the domain, I get the same http status.
The only thing I can think of that would mess with networking is, if Docker Desktop’s utility vm runs in a (nated) network subnet that also exists in your lan, or can be reached though a route .
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.