Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

GitHub Actions Container Retention Policy is Wrongly Configured #123

Open
xfoxfu opened this issue Jul 18, 2023 · 4 comments
Open

GitHub Actions Container Retention Policy is Wrongly Configured #123

xfoxfu opened this issue Jul 18, 2023 · 4 comments

Comments

@xfoxfu
Copy link
Collaborator

xfoxfu commented Jul 18, 2023

Currently the workflow is configured to preserve 5 untagged or COMMIT_SHA1 container images. However, this is not suitable as GZCTF is currently publishing multi-arch + provenance-enabled containers. These containers will have tags applied on a virtual image, which contains metadata of actual images. The actual images is not tagged. Therefore, the images of previous versions is removed.

$ docker pull ghcr.io/gztimewalker/gzctf/gzctf:v0.14.4
v0.14.4: Pulling from gztimewalker/gzctf/gzctf
manifest unknown

Workaround: disable image retention.

Reference:

@GZTimeWalker
Copy link
Owner

Will disabling provenance solve the issue?

 - uses: docker/build-push-action@v4
   with:
     provenance: false
     ...

@xfoxfu
Copy link
Collaborator Author

xfoxfu commented Jul 18, 2023

No, because images are multi-arch.

@GZTimeWalker
Copy link
Owner

No, because images are multi-arch.

May create a PR for this issue? I may not particularly understand how to solve this.

@xfoxfu
Copy link
Collaborator Author

xfoxfu commented Jul 18, 2023

As this is not supported, the only way is to disable retention currently.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants