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
Container Registry blob upload could fail with status code 404 and an error like {"errors":[{"code":"BLOB_UPLOAD_INVALID","message":"blob upload invalid"}]}. It happens when a transient issue (like connection reset) occurs and chunk upload is retried, but can happen for other reasons as well.
If this happens, it's not possible to resume upload - it has to be started all over.
This issue tracks the work to implement resumable upload once the service supports it. We could do this as follows: when a retry fails, get the size of the uploaded blob and resume uploading chunks from that range.
Also, the ACR TSG currently gives guidance to the caller to resume the upload manually in the case of this failure. We will want to remove this guidance if we fully fix the issue in the client.
The text was updated successfully, but these errors were encountered:
Container Registry blob upload could fail with status code 404 and an error like
{"errors":[{"code":"BLOB_UPLOAD_INVALID","message":"blob upload invalid"}]}
. It happens when a transient issue (like connection reset) occurs and chunk upload is retried, but can happen for other reasons as well.If this happens, it's not possible to resume upload - it has to be started all over.
This issue tracks the work to implement resumable upload once the service supports it. We could do this as follows: when a retry fails, get the size of the uploaded blob and resume uploading chunks from that range.
Also, the ACR TSG currently gives guidance to the caller to resume the upload manually in the case of this failure. We will want to remove this guidance if we fully fix the issue in the client.
The text was updated successfully, but these errors were encountered: