Module aws_sdk_ecrpublic::types::error
source · Expand description
Error types that Amazon Elastic Container Registry Public can respond with.
Modules§
- Builders
Structs§
The specified layer upload doesn't contain any layer parts.
The specified image has already been pushed, and there were no changes to the manifest or image tag after the last push.
The specified image digest doesn't match the digest that Amazon ECR calculated for the image.
The image requested doesn't exist in the specified repository.
The specified image is tagged with a tag that already exists. The repository is configured for tag immutability.
The layer digest calculation performed by Amazon ECR when the image layer doesn't match the digest specified.
The layer part size isn't valid, or the first byte specified isn't consecutive to the last byte of a previous layer part upload.
The specified parameter is invalid. Review the available parameters for the API request.
An invalid parameter has been specified. Tag keys can have a maximum character length of 128 characters, and tag values can have a maximum length of 256 characters.
The image layer already exists in the associated repository.
Layer parts must be at least 5 MiB in size.
The specified layers can't be found, or the specified layer isn't valid for this repository.
The operation didn't succeed because it would have exceeded a service limit for your account. For more information, see Amazon ECR Service Quotas in the Amazon Elastic Container Registry User Guide.
The manifest list is referencing an image that doesn't exist.
The registry doesn't exist.
The specified repository already exists in the specified registry.
The repository catalog data doesn't exist.
The specified repository contains images. To delete a repository that contains images, you must force the deletion with the
force
parameter.The specified repository can't be found. Check the spelling of the specified repository and ensure that you're performing operations on the correct registry.
The specified repository and registry combination doesn't have an associated repository policy.
These errors are usually caused by a server-side issue.
The list of tags on the repository is over the limit. The maximum number of tags that can be applied to a repository is 50.
The action isn't supported in this Region.
The upload can't be found, or the specified upload ID isn't valid for this repository.