We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The KBS URI changes in the attestation-agent started merging yesterday (with confidential-containers/attestation-agent#129) and that is a breaking change. As we are still pulling in the latest attestation-agent, if you are using anything involved in the attestation-agent KBS then there might be problems if you created encrypted images and resource files with the old mechanism. The full docs for how to do things the new way are in progress (https://github.com/confidential-containers/attestation-agent/pull/143/files#diff-ec2d1b38fe0166ceb783aa47e49c70f03c837f5671aadae39049d63d53b04c5cR1) but until then the quick workaround is probably to just pull in the 0.4 tag of the attestation-agent.
The text was updated successfully, but these errors were encountered:
podvm: Pin attestation-agent
4f67e88
- Pin attestaton-agent to v0.4.0 to avoid instability Fixes: confidential-containers#697 Signed-off-by: stevenhorsman <[email protected]>
165941e
- Pin attestaton-agent to v0.4.0 to avoid instability Fixes: #697 Signed-off-by: stevenhorsman <[email protected]>
2007e55
eff98cb
stevenhorsman
Successfully merging a pull request may close this issue.
The KBS URI changes in the attestation-agent started merging yesterday (with confidential-containers/attestation-agent#129) and that is a breaking change. As we are still pulling in the latest attestation-agent, if you are using anything involved in the attestation-agent KBS then there might be problems if you created encrypted images and resource files with the old mechanism. The full docs for how to do things the new way are in progress (https://github.com/confidential-containers/attestation-agent/pull/143/files#diff-ec2d1b38fe0166ceb783aa47e49c70f03c837f5671aadae39049d63d53b04c5cR1) but until then the quick workaround is probably to just pull in the 0.4 tag of the attestation-agent.
The text was updated successfully, but these errors were encountered: