CoCoKeyprovider | Failed to publish image #672
Comments
Xynnn007
added a commit
to Xynnn007/guest-components
that referenced
this issue
Aug 15, 2024
As the original repo is now archived, thus we havenot been able to publish the coco keyprovider image for a long time. This commit fixes this issue by changing the image repo. Fixes confidential-containers#672 Signed-off-by: Xynnn007 <[email protected]>
Xynnn007
added a commit
to Xynnn007/guest-components
that referenced
this issue
Aug 16, 2024
As the original repo is now archived, thus we havenot been able to publish the coco keyprovider image for a long time. This commit fixes this issue by changing the image repo. Fixes confidential-containers#672 Signed-off-by: Xynnn007 <[email protected]>
jialez0
pushed a commit
to jialez0/guest-components
that referenced
this issue
Aug 19, 2024
As the original repo is now archived, thus we havenot been able to publish the coco keyprovider image for a long time. This commit fixes this issue by changing the image repo. Fixes confidential-containers#672 Signed-off-by: Xynnn007 <[email protected]>
jialez0
pushed a commit
to jialez0/guest-components
that referenced
this issue
Aug 28, 2024
As the original repo is now archived, thus we havenot been able to publish the coco keyprovider image for a long time. This commit fixes this issue by changing the image repo. Fixes confidential-containers#672 Signed-off-by: Xynnn007 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Everytime a release is cut, the Cut Release Action would build a CoCoKeyprovider image to publish to ghcr.io.
Now starts with 0.7.0, our publishment actually all failed. See
https://github.com/confidential-containers/guest-components/actions/runs/9667189917/job/26668422487#step:4:1826
The image repo is under the archived repo
attestation-agentthus cannot be written.The text was updated successfully, but these errors were encountered: