configure publish profile to push to public AWS ECR
dotnet publish --os linux --arch x64 --configuration Release -p:PublishProfile=<your profile>.pubxml
Error occurs:
error CONTAINER1013: Failed to push to the output registry: CONTAINER1001: Failed to upload blob using PUT https://public.ecr.aws/v2/r4z9b1c4/sdk-containers-test/blobs/uploads/38a481f9-7788-420b-8690-d8ac7531 a60e?&digest=sha256%3A9d21b12d5fab9ab82969054d72411ce627c209257df64b6057016c981e163c30; received status code 'BadRequest'.
Binlog trace:
Last request URI: https://public.ecr.aws/v2/r4z9b1c4/sdk-containers-test/blobs/uploads/38a481f9-7788-420b-8690-d8ac7531a60e?&digest=sha256%3A9d21b12d5fab9ab82969054d72411ce627c209257df64b6057016c981e163c30
Status code: BadRequest
Response headers:
Date: Tue, 04 Jul 2023 13:34:41 GMT
Connection: keep-alive
Docker-Distribution-Api-Version: registry/2.0
Response content: {"errors":[{"code":"BLOB_UPLOAD_INVALID","message":"None of the provided layer digests match the calculated layer digest"}]}
Follow up: https://github.com/dotnet/sdk-container-builds/issues/424
Steps to repro:
dotnet publish --os linux --arch x64 --configuration Release -p:PublishProfile=<your profile>.pubxml
Error occurs:
error CONTAINER1013: Failed to push to the output registry: CONTAINER1001: Failed to upload blob using PUT https://public.ecr.aws/v2/r4z9b1c4/sdk-containers-test/blobs/uploads/38a481f9-7788-420b-8690-d8ac7531 a60e?&digest=sha256%3A9d21b12d5fab9ab82969054d72411ce627c209257df64b6057016c981e163c30; received status code 'BadRequest'.
Binlog trace:
Chunked upload works:
This issue is low priority: