Connection reset by peer
Hi, I am encountering this error while pulling new docker image.
I initially encounter the error while running my endpoint, it'd randomly got stuck in 'in queue' status with the same error
connection reset by peer
. So I tried downgrading my docker image version but it failed on pull. Is there any way to fix this? Thanks23 Replies
Which container registry are you using?
wait i need to confirm this
might be a private repository of my company
but docker pulling and pushing to that repo works fine on other machine
Well the registry is diconnecting the connection from RunPod, so maybe you have a self hosted registry with a firewall that is blocking RunPod but allowing internal traffic.
it might not be a problem with the registry, I tried switching back to the last image that is cached in the system, the endpoint works but sometimes it would yield the same error as such
and also a long traceback
is this error something of my end?
Which region is the endpoint in? There might be a networking issue in that region.
the traceback refers to the code of runpod handler library
it's global
Oh, that makes it very difficult to debug, guess someone from RunPod team will have to look into it for you.
This is the endpoint id, right? s42u5cq5ywrn55
true, I have also contacted support via the website, they're on it as well
I would also try terminating that worker (j0lijso11z3hz8) and see if you get a new one in a different region.
Oh thats good 👍
ah ok i see, will try that
thankyou, prod and dev services are down so im looking everywhere hahah
have you fixed this problem yet?
Not yet
Sometimes it'd work but any other time it'd yield that error
Seems @pazanchick has the same issue
is availability the problem tho?
Maybe. I wouldn't choose the ones that are unavailable to be honest.
kk
I got the same issue during the day. I deployed in europe. At first it could be an availability problem (was using network volume). I dropped the network volume, and got the same error on 2 different endpoint that I have deployed.
I have been talking viachat with a team member of runpod. It seems they are on it
Even we are facing it at the moment. Any updates on it?
Solution
now it's stable, i think they fixed it
great to hear that hahah
yeah hahahah, things are ok up till now thanks all