1 |
On Sat, 10 Dec 2022 15:51:17 -0500 |
2 |
Mansour Al Akeel <mansour.alakeel@×××××.com> wrote: |
3 |
|
4 |
> Andreas, |
5 |
> |
6 |
> Thank you very much. In fact I didn't go that deep yet, and not sure if I |
7 |
> should. I just found that the url is not accessible even from a browser. |
8 |
> Googling a bit, tells me there is no clear URL for docker-registry and |
9 |
> possibly this one is outdated. I will continue looking around to confirm |
10 |
> what the current default repo should be. If you have any suggestions, |
11 |
> please let me know. |
12 |
> |
13 |
> |
14 |
> localhost in ~ |
15 |
> ○ → curl -k -v https://registry-1.docker.io/v2/ |
16 |
> * Trying 34.228.211.243:443... |
17 |
> |
18 |
> * connect to 34.228.211.243 port 443 failed: Connection timed out |
19 |
> * Failed to connect to registry-1.docker.io port 443 after 129401 ms: |
20 |
> Couldn't connect to server |
21 |
> * Closing connection 0 |
22 |
> curl: (28) Failed to connect to registry-1.docker.io port 443 after 129401 |
23 |
> ms: Couldn't connect to server |
24 |
|
25 |
|
26 |
You have a a strange DNS resolution. The IP address 34.227.211.243 |
27 |
seems wrong. Here is what I see when I look at the DNS records: |
28 |
andreas@localhost ~$ dig registry-1.docker.io |
29 |
|
30 |
; <<>> DiG 9.16.33 <<>> registry-1.docker.io |
31 |
;; global options: +cmd |
32 |
;; Got answer: |
33 |
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11419 |
34 |
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 |
35 |
|
36 |
;; OPT PSEUDOSECTION: |
37 |
; EDNS: version: 0, flags:; udp: 4096 |
38 |
;; QUESTION SECTION: |
39 |
;registry-1.docker.io. IN A |
40 |
|
41 |
;; ANSWER SECTION: |
42 |
registry-1.docker.io. 13 IN A 34.205.13.154 |
43 |
registry-1.docker.io. 13 IN A 44.205.64.79 |
44 |
registry-1.docker.io. 13 IN A 3.216.34.172 |
45 |
|
46 |
;; Query time: 10 msec |
47 |
;; SERVER: 79.143.183.251#53(79.143.183.251) |
48 |
;; WHEN: Sun Dec 11 06:56:50 CET 2022 |
49 |
;; MSG SIZE rcvd: 97 |
50 |
|
51 |
I am not sure |
52 |
Not sure where you get the wrong IP from, but it is a DNS issue. |