Error response from daemon: Get "https://registry-1.docker.io/v2/"

My OMV is running fine a week ago with docker and portainer, and when i tried to pull some images for some project i encounter some problems.

When i tried to pull/search/run with docker command i get the following error

docker pull hello-world

Error response from daemon: Get "https://registry-1.docker.io/v2/": read tcp 192.168.0.3:33434->44.194.5.25:443: read: connection reset by peer

docker search hello-world

Error response from daemon: Get "https://index.docker.io/v1/search?q=hello-world&n=25": read tcp 192.168.0.3:44900->44.205.66.155:443: read: connection reset by peer

docker run hello-world

Unable to find image 'hello-world:latest' locally

docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": read tcp 192.168.0.3:49590->44.207.51.64:443: read: connection reset by peer.

Zitat von Zoki

Network error on docker, wait a bit.

its been 3 days now, is the problem on my end or docker?

Zitat von KM0201

Are you sure your server is online?

ping -c5 aol.com

It is working fine for me...

Code

ken0201@openmediavault:~$ su -
Password: 
root@openmediavault:~# docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
2db29710123e: Pull complete 
Digest: sha256:53f1bbee2f52c39e41682ee1d388285290c5c8a76cc92b42687eecf38e0af3f0
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (amd64)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/

root@openmediavault:~# 

Alles anzeigen

Alles anzeigen

the ping gives me

PING aol.com (98.136.103.23) 56(84) bytes of data.

64 bytes from w2.src.vip.gq1.yahoo.com (98.136.103.23): icmp_seq=1 ttl=48 time=182 ms

64 bytes from w2.src.vip.gq1.yahoo.com (98.136.103.23): icmp_seq=1 ttl=48 time=182 ms (DUP!)

64 bytes from w2.src.vip.gq1.yahoo.com (98.136.103.23): icmp_seq=2 ttl=48 time=179 ms

64 bytes from w2.src.vip.gq1.yahoo.com (98.136.103.23): icmp_seq=2 ttl=48 time=179 ms (DUP!)

64 bytes from w2.src.vip.gq1.yahoo.com (98.136.103.23): icmp_seq=3 ttl=48 time=179 ms

64 bytes from w2.src.vip.gq1.yahoo.com (98.136.103.23): icmp_seq=3 ttl=48 time=179 ms (DUP!)

64 bytes from w2.src.vip.gq1.yahoo.com (98.136.103.23): icmp_seq=4 ttl=48 time=182 ms

64 bytes from w2.src.vip.gq1.yahoo.com (98.136.103.23): icmp_seq=4 ttl=48 time=182 ms (DUP!)

64 bytes from w2.src.vip.gq1.yahoo.com (98.136.103.23): icmp_seq=5 ttl=48 time=182 ms

--- aol.com ping statistics ---

5 packets transmitted, 5 received, +4 duplicates, 0% packet loss, time 4005ms

rtt min/avg/max/mdev = 178.844/180.623/182.204/1.562 ms

Zitat von KM0201

Well you're online. Are you sure docker is completely installed and running?

systemctl status docker

● docker.service - Docker Application Container Engine

Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)

Drop-In: /etc/systemd/system/docker.service.d

└─http-proxy.conf, https-proxy.conf, waitAllMounts.conf

Active: active (running) since Thu 2022-07-14 15:59:31 PST; 41min ago

TriggeredBy: ● docker.socket

Docs: https://docs.docker.com

Main PID: 738 (dockerd)

Tasks: 10

Memory: 124.1M

CPU: 2.282s

CGroup: /system.slice/docker.service

└─738 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

Jul 14 15:59:31 JohnAlvinServer dockerd[738]: time="2022-07-14T15:59:31.214356978+08:00" level=info msg="Docker daemon" commit=a89b842 graphdriver(s)=overlay2 version=20.10.17

Jul 14 15:59:31 JohnAlvinServer dockerd[738]: time="2022-07-14T15:59:31.215126741+08:00" level=info msg="Daemon has completed initialization"

Jul 14 15:59:31 JohnAlvinServer systemd[1]: Started Docker Application Container Engine.

Jul 14 15:59:31 JohnAlvinServer dockerd[738]: time="2022-07-14T15:59:31.311147005+08:00" level=info msg="API listen on /run/docker.sock"

Jul 14 16:00:43 JohnAlvinServer dockerd[738]: time="2022-07-14T16:00:43.011072777+08:00" level=warning msg="Error getting v2 registry: Get \"https://registry-1.docker.io/v2/\": read tcp 192.168.0.3:60278->44.19>

Jul 14 16:00:43 JohnAlvinServer dockerd[738]: time="2022-07-14T16:00:43.011199749+08:00" level=info msg="Attempting next endpoint for pull after error: Get \"https://registry-1.docker.io/v2/\": read tcp 192.168>

Jul 14 16:00:43 JohnAlvinServer dockerd[738]: time="2022-07-14T16:00:43.019860958+08:00" level=error msg="Handler for POST /v1.41/images/create returned error: Get \"https://registry-1.docker.io/v2/\": read tcp>

Jul 14 16:00:43 JohnAlvinServer dockerd[738]: time="2022-07-14T16:00:43.650890889+08:00" level=warning msg="Error getting v2 registry: Get \"https://registry-1.docker.io/v2/\": read tcp 192.168.0.3:36452->44.20>

Jul 14 16:00:43 JohnAlvinServer dockerd[738]: time="2022-07-14T16:00:43.651016979+08:00" level=info msg="Attempting next endpoint for pull after error: Get \"https://registry-1.docker.io/v2/\": read tcp 192.168>

Jul 14 16:00:43 JohnAlvinServer dockerd[738]: time="2022-07-14T16:00:43.659338007+08:00" level=error msg="Handler for POST /v1.41/images/create returned error: Get \"https://registry-1.docker.io/v2/\": read tcp>

Zitat von KM0201

that's weird.

Does the command omv-upgrade

do anything?

root@JohnAlvinServer:~# omv-upgrade

Get:1 file:/var/cache/openmediavault/archives InRelease

Ign:1 file:/var/cache/openmediavault/archives InRelease

Get:2 file:/var/cache/openmediavault/archives Release

Ign:2 file:/var/cache/openmediavault/archives Release

Get:3 file:/var/cache/openmediavault/archives Packages

Ign:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:3 file:/var/cache/openmediavault/archives Packages

Ign:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:3 file:/var/cache/openmediavault/archives Packages

Ign:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:3 file:/var/cache/openmediavault/archives Packages

Ign:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:3 file:/var/cache/openmediavault/archives Packages

Ign:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:3 file:/var/cache/openmediavault/archives Packages

Ign:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Get:3 file:/var/cache/openmediavault/archives Packages

Get:4 file:/var/cache/openmediavault/archives Translation-en

Ign:4 file:/var/cache/openmediavault/archives Translation-en

Hit:5 https://openmediavault.github.io/packages shaitan InRelease

Hit:6 https://openmediavault-plugin-…github.io/packages/debian shaitan InRelease

Hit:7 http://security.debian.org/debian-security bullseye-security InRelease

Hit:8 https://download.docker.com/linux/debian bullseye InRelease

Hit:9 http://deb.debian.org/debian bullseye InRelease

Get:10 http://deb.debian.org/debian bullseye-updates InRelease [39.4 kB]

Hit:11 https://openmediavault-plugin-…github.io/packages/debian shaitan-testing InReleaseGet:12 http://httpredir.debian.org/debian bullseye-backports InRelease [44.2 kB]

Hit:13 http://packages.openmediavault.org/public shaitan InRelease

Get:14 http://httpredir.debian.org/debian bullseye-backports/main amd64 Packages.diff/Index [63.3 kB]

Get:15 http://httpredir.debian.org/debian bullseye-backports/main amd64 Packages T-2022-07-14-0810.04-F-2022-07-14-0810.04.pdiff [193 B]

Get:15 http://httpredir.debian.org/debian bullseye-backports/main amd64 Packages T-2022-07-14-0810.04-F-2022-07-14-0810.04.pdiff [193 B]

Fetched 147 kB in 4s (39.1 kB/s)

Reading package lists... Done

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

Calculating upgrade... Done

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Zitat von KM0201

Are you using a proxy, or trying to run docker on a virtual machine by chance?

Only thing I really found on that error is this..

https://community.ui.com/quest…aa-4c3f-83fc-8ff2afd3ac2c

I'm not using a proxy.

The docker is run inside the OMV, and the OMV is not installed in a VM.

Zitat von Zoki

Start from the very beginning and check if the server can be reached:

nslookup registry-1.docker.io

ping registry-1.docker.io

sorry for the late response here is the results:

nslookup registry-1.docker.io

Server: 8.8.8.8

Address: 8.8.8.8#53

Non-authoritative answer:

Name: registry-1.docker.io

Address: 44.207.96.114

Name: registry-1.docker.io

Address: 44.207.51.64

Name: registry-1.docker.io

Address: 44.194.5.25

ping registry-1.docker.io

--- registry-1.docker.io ping statistics ---

333 packets transmitted, 0 received, 100% packet loss, time 339960ms

Zitat von Zoki

Are you living in a place which blocks AWS services?

Try

Code

curl https://registry-1.docker.io/v2/ && echo Works

and check if you are using a proxy cat /etc/docker/daemon.json and docker info | grep Proxy

Im not sure if im block by AWS services because docker pull was running normally like weeks ago

curl https://registry-1.docker.io/v2/ && echo Works

curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to registry-1.docker.io:443

cat /etc/docker/daemon.json

{

"data-root": "/var/lib/docker"

}

docker info | grep Proxy

No output

Zitat von Zoki

it looks like you are blocken.

What is the result of docker login

Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one.

Username: myusername

Password: mypassword

Error response from daemon: Get "https://registry-1.docker.io/v2/": read tcp 192.168.0.3:45806->44.207.96.114:443: read: connection reset by peer