Fix image workflow #8534
Fix image workflow #8534
Conversation
Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
|
Hi @gabriel-samfira. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Test run in my fork: https://github.com/gabriel-samfira/containerd/actions/runs/5018372122/jobs/8997693957 |
|
This action will have to be run manually. |
Running now 🤞🏻 @gabriel-samfira 😄 |
It worked! Thanks! https://github.com/containerd/containerd/pkgs/container/volume-copy-up/95526048?tag=2.2 |
This change updates the default windows image SKU used to the
latesttag. This should always be around, and should be regularly updated to something close to the actual latest image available. For generating images, thelatesttag should be safe to use.We also disable provenance. See: docker/buildx#1509 (comment)
One important note before triggering this workflow. Github has introduced a new permissions system for
ghcr.io. Before running this workflow, someone with write access to the repo will have to navigate to https://ghcr.io/containerd/volume-copy-up and https://ghcr.io/containerd/volume-ownership and click onPackage settingson the right hand side. Once there, underActions repository access, you will need to addcontainerd/containerdas a repository, withwriteaccess.