-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"rad bicep publish" Fails to Publish Bicep Files to ECR #7855
Comments
👋 @vishwahiremat Thanks for filing this bug report. A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server. For more information on our triage process please visit our triage overview |
👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up. We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue. For more information on our triage process please visit our triage overview |
Possibly a similar issue that was worked around: https://github.com/devcontainers/cli/issues/814 |
# Description ECR thorws following error when Data is nil, updating the data to a empty descriptor. ``` Something went wrong Cause: PUT " https://<account-name>.dkr.ecr.us-east-2.amazonaws.com/v2/test-private-ecr/blobs/uploads/47552bfb-e8f7-41ad-9c07-310446dc14?digest=sha256%3Ae3b0c44298fc1c149afbf4c8996fb927ae41e4649b934ca495991b7852b855": response status code 400: blob upload invalid: The upload with id '47552bfb-e8f7-41ad-9c07-314186dc14' in the repository with name 'test-ecr' in registry with id '<account-name>' cannot be completed because it does not have any parts. ``` ## Type of change <!-- Please select **one** of the following options that describes your change and delete the others. Clearly identifying the type of change you are making will help us review your PR faster, and is used in authoring release notes. If you are making a bug fix or functionality change to Radius and do not have an associated issue link please create one now. --> - This pull request fixes a bug in Radius and has an approved issue (issue link required). - This pull request adds or changes features of Radius and has an approved issue (issue link required). - This pull request is a minor refactor, code cleanup, test improvement, or other maintenance task and doesn't change the functionality of Radius (issue link optional). <!-- Please update the following to link the associated issue. This is required for some kinds of changes (see above). --> Fixes: #7855 --------- Signed-off-by: Vishwanath Hiremath <[email protected]>
Steps to reproduce
aws ecr get-login-password --region us-east-2 | docker login --username AWS --password-stdin <account-name>.dkr.ecr.us-east-2.amazonaws.com
rad bicep publish --file test/testrecipes/test-bicep-recipes/rabbitmq-recipe.bicep --target br:<account-name>.dkr.ecr.us-east-2.amazonaws.com/test-ecr:latest
Observed behavior
Throws
blob upload invalid
errorFailed to publish Bicep file "test/testrecipes/test-bicep-recipes/rabbitmq-recipe.bicep" to "<account-name>.dkr.ecr.us-east-2.amazonaws.com/test-ecr:1.0" Something went wrong Cause: PUT "https://<account-name>.dkr.ecr.us-east-2.amazonaws.com/v2/test-private-ecr/blobs/uploads/47552bfb-e8f7-41ad-9c07-310446dc14?digest=sha256%3Ae3b0c44298fc1c149afbf4c8996fb927ae41e4649b934ca495991b7852b855": response status code 400: blob upload invalid: The upload with id '47552bfb-e8f7-41ad-9c07-314186dc14' in the repository with name 'test-ecr' in registry with id '<account-name>' cannot be completed because it does not have any parts.
Desired behavior
Should be able to successfully upload bicep to ECR
Workaround
No response
rad Version
RELEASE VERSION BICEP COMMIT
0.37.0 v0.37.0 0.29.47 b1a7822
Operating system
No response
Additional context
No response
Would you like to support us?
AB#13092
The text was updated successfully, but these errors were encountered: