You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the issue: skipExistingImages is supposed to make the error of having already pushed the image go away, but I still get:
Execution failed for task ':name:jib'.
> com.google.cloud.tools.jib.plugins.common.BuildStepsExecutionException:
Tried to push image manifest for blablabla.amazonaws.com/some/name:theversion but failed because:
Registry may not support pushing OCI Manifest or Docker Image Manifest Version 2, Schema 2
I've verified that skipExistingImages is correctly set to true when gradle is invoked by adding the following print in one of my build.gradle.kts files:
The problem typically occurs if there's some flakiness in the CI so a few of the images get pushed successfully, which during a retry will cause a failure due to already pushed images.
The workaround is ofc to just commit something which changes the hash used as tag allowing the build to complete, but it's an inconvenience compared to just retry.
Expected behavior:
Complete silence and exit 0, or some log that says the image already exists.
Steps to reproduce:
Create an immutable AWS ECR repository entry
Run jib task to push
In my case this produces an Image Index with the tag, plus two untagged Image entries, one for each of arm64 and x64.
Execution failed for task ':name:jib'.
> com.google.cloud.tools.jib.plugins.common.BuildStepsExecutionException:
Tried to push image manifest for blablabla.amazonaws.com/some/name:theversion but failed because:
Registry may not support pushing OCI Manifest or Docker Image Manifest Version 2, Schema 2
Additional Information:
The text was updated successfully, but these errors were encountered:
Environment:
Description of the issue:
skipExistingImages
is supposed to make the error of having already pushed the image go away, but I still get:I've verified that
skipExistingImages
is correctly set to true when gradle is invoked by adding the following print in one of mybuild.gradle.kts
files:This prints
true
.The problem typically occurs if there's some flakiness in the CI so a few of the images get pushed successfully, which during a retry will cause a failure due to already pushed images.
The workaround is ofc to just commit something which changes the hash used as tag allowing the build to complete, but it's an inconvenience compared to just retry.
Expected behavior:
Complete silence and exit 0, or some log that says the image already exists.
Steps to reproduce:
jib
task to pushjib-gradle-plugin
Configuration:Log output:
Additional Information:
The text was updated successfully, but these errors were encountered: