Direkt zum Inhalt

error from registry: Invalid parameter at 'ImageManifest' failed to satisfy constraint: 'Invalid JSON syntax'

0

我在push image是发现如下错误, 但是其他image可以正常push到我的repor里

aws ecr-public get-login-password --region us-east-1 | docker login --username AWS --password-stdin public.ecr.aws Login Succeeded

docker push public.ecr.aws/m3q8r0k4/daiy4poc/alluxio-operator:3.2.4 The push refers to repository [public.ecr.aws/m3q8r0k4/daiy4poc/alluxio-operator] 0499fc56f5e2: Layer already exists 5f70bf18a086: Layer already exists 64c9374deb75: Layer already exists c80c903d7b92: Layer already exists 9a87cc333fe5: Layer already exists c857a567d822: Layer already exists 33e32f97e15b: Layer already exists f635df5c5a4d: Layer already exists 69e4e9f2b396: Layer already exists cefdb45dcaa2: Layer already exists 2bedb4bd3f95: Layer already exists d9ae471306bb: Layer already exists fbc00c0eed09: Layer already exists f72e9ef79735: Layer already exists 7ebef30162f6: Layer already exists error from registry: Invalid parameter at 'ImageManifest' failed to satisfy constraint: 'Invalid JSON syntax'

gefragt vor 4 Monaten97 Aufrufe
1 Antwort
0

The error you're encountering when pushing your Docker image to Amazon ECR is related to an invalid image manifest. The error message "Invalid parameter at 'ImageManifest' failed to satisfy constraint: 'Invalid JSON syntax'" indicates that there's an issue with the JSON format of your Docker image manifest.

This can happen for several reasons:

  1. The Docker image might be corrupted or have an invalid format
  2. There might be compatibility issues between your Docker version and ECR
  3. The image might have been built with non-standard configurations

Here are some steps you can try to resolve this issue:

  1. Rebuild the Docker image from scratch to ensure it's properly formatted
  2. Try using a different Docker tag for this specific image
  3. Verify that you're using an up-to-date version of Docker
  4. If you're using a multi-architecture image, ensure it's properly configured
  5. Try to export the image and then reload it before pushing:
docker save alluxio-operator:3.2.4 > alluxio.tar
docker load < alluxio.tar
  1. Check if there are any special characters or formatting issues in your Dockerfile

Since you mentioned that other images push successfully to your repository, the issue is likely specific to this particular image rather than with your authentication or repository configuration.
Sources
Pushing docker image through Git Hub enterprise runner to aws ECR private repo | AWS re:Post
Why can’t I do unauthenticated pull from public ECR? | AWS re:Post

beantwortet vor 4 Monaten

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.