Closed MikeMcC399 closed 4 months ago
@jennifer-shehane
I don't understand why this issue has occurred and it is in an area where I have no experience! I can't tell if was a CircleCI glitch or something else.
If it is not addressed it will prevent any new cypress/factory
images from being published.
Depending on the root cause it may also affect the automatic publication of cypress/base
, cypress/browsers
and cypress/included
images.
There is a possibility that the image cypress/factory:4.0.1
is corrupted through 3 parallel-running PRs which each checked if there was an image cypress/factory:4.0.1
present, found there was not, and then each built one and published it:
cypress/factory:4.0.1
cypress/factory:4.0.1
cypress/factory:4.0.1
The 2nd of the PRs https://github.com/cypress-io/cypress-docker-images/pull/1079 also effectively bumped the Docker client version from Docker 20.10.18
to 26.0.2
. This might have all been too much in one go!
Perhaps cypress/factory:4.0.1
should be manually deleted so that it can be recreated?
It seems there were some breaking changes in https://github.com/docker/buildx
After this is merged it will require a manual delete of the incompatible cypress/factory:4.0.1 image
K, let me know if that works and if the deletion is required.
@jennifer-shehane
Sorry that a revert was necessary, but at least only one image was caught up in this. I only noticed by accident when I was looking into another failure, as the workflow itself does not return an error. It's only visible when you examine the logs manually.
https://app.circleci.com/pipelines/github/cypress-io/cypress-docker-images/1967/workflows/63050ae3-636c-46a2-a570-c5a14187d2e1/jobs/59867 is showing success
BUT in "Check if image for factory exists or Docker hub does not respond" the incompatibility shows up as expected:
RestError [InvalidContentError]: unsupported schema version 2 in cypress/factory:4.0.1 manifest
So, yes please, deletion of cypress/factory:4.0.1
on Docker Hub is needed. I don't think it checks on AWS, so I'm guessing that it will just overwrite there.
I deleted the 4.0.1 tag in cypress/factory. Hopefully that worked.
@jennifer-shehane
I deleted the 4.0.1 tag in cypress/factory. Hopefully that worked.
Thank you! That should be good, and the next merge to master will test that out.
In the meantime I checked by hand and docker-image-not-found
is happy again! 😃
$ docker-image-not-found --repo cypress/factory:4.0.1
got an error fetching info about Docker image docker.io/cypress/factory:4.0.1
Got definite NotFoundError
exiting with code 0
It does however still fail when no tag is defined, which defaults to latest
, and latest
is still linked to the problematic manifest. I expect that will get overwritten at the next release. We'll see!
Closing as resolved. I will be monitoring what happens next!
Edit:
Issue
The CircleCI workflow job "Push Factory Image" is failing to get the status of
cypress/factory:4.0.1
from Docker Hub cypress/factory.The error is
Examining the manifest of
cypress/factory:4.0.1
with the following command shows that it differs in format from the manifest forcypress/factory:4.0.0
(and fromcypress/base
,cypress/browsers
andcypress/included
)shows
instead of
Logs
https://app.circleci.com/pipelines/github/cypress-io/cypress-docker-images/1959/workflows/3c12d584-8378-4f1d-8722-bcc504b21e2d/jobs/59620 from PR
shows
Analysis
cypress/factory:4.0.1
was published through PR https://github.com/cypress-io/cypress-docker-images/pull/1078Manifest
cypress/factory:4.0.1
cypress/factory:4.0.0
Log Push Factory Image for 4.0.1
https://app.circleci.com/pipelines/github/cypress-io/cypress-docker-images/1944/workflows/d32dcb15-f148-4cf7-a4d1-3b1f48ab6141/jobs/59206
Check for existence
building Docker image for target factory