You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experiencing an issue when trying to pull a large Docker image on the RunPod cloud platform. The operation fails with the following error message: failed to pull image: expected HTTP 206 from byte range request.
Interestingly, I'm able to pull the same image successfully using the Docker client locally. The problem seems to occur only with larger images on the cloud platform.
Steps to Reproduce:
Attempt to pull a large Docker image on the RunPod cloud platform. Observe the error message related to HTTP 206.
Expected Behavior:
The large image should be pulled successfully on the RunPod cloud platform, as it does with the Docker client locally.
Actual Behavior:
The pull operation fails with an HTTP 206 error on the cloud platform when dealing with large images.
Thank you for looking into this issue. Your assistance in resolving this would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
I think the runtime that they have might be using ranged pulls which serverless-registry doesn't support yet. I will take a look and have an implementation tomorrow hopefully.
I'm experiencing an issue when trying to pull a large Docker image on the RunPod cloud platform. The operation fails with the following error message: failed to pull image: expected HTTP 206 from byte range request.
Interestingly, I'm able to pull the same image successfully using the Docker client locally. The problem seems to occur only with larger images on the cloud platform.
Steps to Reproduce:
Attempt to pull a large Docker image on the RunPod cloud platform. Observe the error message related to HTTP 206.
Expected Behavior:
The large image should be pulled successfully on the RunPod cloud platform, as it does with the Docker client locally.
Actual Behavior:
The pull operation fails with an HTTP 206 error on the cloud platform when dealing with large images.
Thank you for looking into this issue. Your assistance in resolving this would be greatly appreciated.
The text was updated successfully, but these errors were encountered: