Docker push to microk8s registry "connection reset by peer"

General Discussions microk8s
1

Hi,
I have installed microk8s on linux server in local network. I also use registry.
Now till few days ago pushing to docker registry works fine. But then suddenly it breaks with error:

“read: connection reset by peer”

microkol@KOL1197:/mnt/c/developPython/salonitBaseline$ docker push setup02:32000/salonit-base --all-tags
The push refers to repository [setup02:32000/salonit-base]
e2de4d2dd9c8: Layer already exists
be44c3af6619: Layer already exists
7055d144143f: Layer already exists
261ed617305c: Layer already exists
37b14643f733: Layer already exists
d85b356ec3b5: Layer already exists
Patch “http://setup02:32000/v2/salonit-base/blobs/uploads/655ebfbc-64a9-4756-a9e5-1ae39b7e4196?_state=acv3jeDpx6yFrBQjZr9otmssYuvayzLhUgqHnMLc-fZ7Ik5hbWUiOiJzYWxvbml0LWJhc2UiLCJVVUlEIjoiNjU1ZWJmYmMtNjRhOS00NzU2LWE5ZTUtMWFlMzliN2U0MTk2IiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDIzLTA2LTE0VDA0OjU4OjQ3Ljg0NDk2MTM1NVoifQ%3D%3D”: read tcp 172.31.31.73:45218->10.10.8.80:32000: read: connection reset by peer

I have tried to disable registry and clean its space, but the problem still existst. Meanwhile I can easily push to azure private repository same image.

Does anybody know how to solve this error?

Regards
Gašper

2

even i am getting the same issue in the pod events i am facing the issue
(combined from similar events): Failed to pull image “registry.example.com/custom-postgres-with-mc-a3dy”: failed to pull and unpack image “registry.example.com/custom-postgres-with-mc-a3dy:latest”: failed to resolve reference “registry.example.com/custom-postgres-with-mc-a3dy:latest”: failed to do request: Head “https://registry.example.com/v2/custom-postgres-with-mc-a3dy/manifests/latest”: read tcp x.x.x.x:54378->x.x.x.x:443: read: connection reset by peer

debug steps:
docker login in my local system worked
able to push image to registry frm local worked
telenet connection on 443 it worked on my local

assumption
ssh in node and tried to login uisng docker login got reset by peer

i am unable to resolve this issue need to support

recently i added ovh openstack loadbalancer and in listeners i pool i added proxy protocal to capture source ip for clients