Handle Blob Create when the underlying registry doesn't provide 'Docker-Upload-UUID' #2927
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some registries, such as ECR don't provide a
Docker-Upload-UUID
HTTP header when starting a blob upload. So we can't rely on that, which then fails when we try to generate theLocation
header we return (in blobupload.go).This fallbacks to try reading the UUID from the Location header returned by the underlying service. If we still don't have any UUID, it then returns an error.
I didn't remove @dmcgowan's TODO because we're technically still not checking for invalid UUID, only for empty strings.