-
Notifications
You must be signed in to change notification settings - Fork 30
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
Action deletes manifests of tagged images #97
Comments
Associated manifests for multi-arch builds do not have tags associated with them. This is partially described in https://github.com/snok/container-retention-policy?tab=readme-ov-file#safely-handling-multi-platform-multi-arch-packages. I hope to fully support this case out of the box in the future, but for now it's up to users to specify which images are safe to delete, if using this with multi-arch packages |
@sondrelg we are not currently building multi-arch, just In our case, it appears that layers required by tagged images are being deleted when |
How are you building images? If you run |
@sondrelg Thank you for planning to implement this in the future. It would be really helpful for us. I appreciate your package and the obvious time it takes to maintain. |
We have a github action that builds images and pushes to GHCR. I confirm that it is only |
I just had to manually rebuild and push an image for which I was getting the manifest unknown issue: $ docker pull ghcr.io/bcgov/traction-plugins-acapy:0.5.0
0.5.0: Pulling from bcgov/traction-plugins-acapy
What's next:
View a summary of image vulnerabilities and recommendations → docker scout quickview ghcr.io/bcgov/traction-plugins-acapy:0.5.0
manifest unknown This is the output of the push command: $ docker push ghcr.io/bcgov/traction-plugins-acapy:0.5.0
The push refers to repository [ghcr.io/bcgov/traction-plugins-acapy]
6c3a6c30ab10: Pushed
a415a1e9b727: Pushed
c44bb3085bb4: Pushed
e2d07531cbd5: Pushed
ef9d8b9e32d4: Pushed
edd31a27bbaa: Pushed
93a758defe24: Pushed
b13ae6128e6c: Layer already exists
f2ffdea5e144: Layer already exists
984442eb3b08: Layer already exists
a07804329048: Layer already exists
5f501f5e0646: Layer already exists
4f9788281efc: Layer already exists
0b28da556a7b: Layer already exists
d71c1661cd45: Layer already exists
5f70bf18a086: Layer already exists
92d34798822d: Layer already exists
30cae9910911: Layer already exists
76f38e225d85: Layer already exists
60830b5bc585: Layer already exists
e8b19277192f: Layer already exists
c11d0a8908db: Layer already exists
6f697f52d485: Layer already exists
0.5.0: digest: sha256:079d6fe9cac1c04933e3103adea4076623c33de39ac0332a84f32f1f615ee360 size: 5131 Several layers were missing, as suspected, however the image is/was still listed in the package list. Inspecting the image yields the following:
|
I have set-up an action to prune old untagged images as follows:
My expectation would be for the action to only delete images that do not have an explicit tag and are older than one month, however it appears that it is also removing other images as well, possibly layers that are required by tagged images. The symptom we're experiencing is that the image tag is available in the GHCR, however trying to pull the tagged image results in a
manifest unknown
error.The text was updated successfully, but these errors were encountered: