While following the tutorial at dockerdocks get-started introduction develop-with-containers I encountered an error when trying to run the docker compose watch in docker terminal. The error is given below:
getting-started-todo-app> docker compose watch
[+] Running 0/3
proxy Pulling 6.6s
mysql Pulling 6.6s
phpmyadmin Pulling 6.6s
failed to copy: httpReadSeeker: failed open: failed to do request: Get "docker-images-prod.30f8896e0***.r2.cloudflarestorage com/registry-v2/docker/registry/v2/blobs/sha256/51/5ff7e6391564ec78048cf3/data?X-Amz-Algorithm=&z-Credential=Date=23Z&X-Amz-Expires=1z-SignedHeaders=host&X-Amz-Signature=": dialing docker-images-prod.6aa32f56.r2.cloudflarestorage.com:443 container via direct connection because static system has no HTTPS proxy: connecting to docker images prod.6a56.r2.cloudflarestorage com:443: dial tcp: lookup docker-images-prod.6aa30f8b08e16409b46e0173d6de2f56.r2.cloudflarestorage com: no such host
How do I resolve this error? When I ran an image in docker for the 1st time, I got a pop up that firewall blocked some features of docker backend and it was asking to allow or cancel. I clicked on cancel but, later through allow an app through firewall enabled the exception for private networks only. Does that have anything to do with the error?
I tried using docker build -t todo-app .
[+] Building 7.7s (3/3) FINISHED docker:desktop-linux
=> [internal] load build definition from Dockerfile 0.2s
=> => transferring dockerfile: 3.22kB 0.0s
=> ERROR [internal] load metadata for docker io/library/node:22 7.2s
=> [auth] library/node:pull token for registry-1.docker io 0.0s
[internal] load metadata for docker io/library/node:22:
Dockerfile:7
5 | # and provides common configuration for all stages, such as the working dir.
6 | ###################################################
7 | >>> FROM node:22 AS base
8 | WORKDIR /usr/local/app
ERROR: failed to build: failed to solve: node:22: failed to resolve source metadata for docker io/library/node:22: failed to copy: httpReadSeeker: failed open: failed to do request: Get âhttpsâ dialing docker-images-prod.6aa30f8b08.cloudflarestorage com:443 container via direct connection because static system has no HTTPS proxy: connecting to docker-images-prod.6aa30f.cloudflarestorage com:443: dial tcp: lookup docker-images-prod.6aa30f56.r2.cloudflarestorage com: no such host
I tried using the same build command on another dockerfile that got I from github and it ran successfully
PS C:\WINDOWS\system32> ping -n 1 docker-images-prod.6aa30f8b08e16409b46e0173d6de2f56.r2.cloudflarestorage.
Ping request could not find host docker-images-prod.6aa30f8b08e16409b46e0173d6de2f56.r2.cloudflarestorage. Please check the name and try again.
Please, format your posts according to the following guide: How to format your forum posts
It will help the spamfilter not to block you.
In short: please, use </> button to share codes, terminal outputs, error messages or anything that can contain special characters which would be interpreted by the MarkDown filter. Use the preview feature to make sure your text is formatted as you would expect it and check your post after you have sent it so you can still fix it.
Example code block:
```
echo "I am a code."
echo "An athletic one, and I wanna run."
```
After fixing your post, please send a new comment so people are notified about the fixed content.
You bypass the dns server that causes the problem. I consider this is a workaround at best.
Depending whether you depend on local hostname or domain resolution, the workaround will prevent you from accessing devices in your local network using the host or domain name.
The dns server in your network responded with Query refused, which is either caused by a miss configuration, or could be deliberately configured by administrators to enforce compliance policies. In the later case your workaround would be a direct breach of compliance policies. You should realy talk to whoever maintains the dns server reliance.reliance to find a real solution.