-
Notifications
You must be signed in to change notification settings - Fork 476
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
Update plugin_agent_workloadattestor_docker.md #5040
Conversation
Signed-off-by: Raisson Souto <raisson.souto@ccc.ufcg.edu.br>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @raissonsouto for this.
There may be a confusion here. The docker:image_id
selector should generate a selector that is a digest. It's a computed (truncated) SHA256 hash of the image configuration object. It shouldn't be the REPOSITORY:TAG.
Have you seen this selector to be something different than a digest?
This documentation is based in my experience with SPIRE. I was using a Envoy proxy within docker and using a SPIRE agent in the host machine with the docker workload attestator and when I tried to use the selector If you want to try yourself, these are the files used: server.conf
agent.conf
compose.yaml:
envoy.yaml
Steps
|
Thank you @raissonsouto. Could you share SPIRE Agent logs when the attestation happens? Particularly, the DEBUG log message |
|
Another useful information, I'm using SPIRE 1.9.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @raissonsouto for bringing this up. I was able to reproduce the same kind of output for the image_id
selector, indicating the image name. I filed #5114 to address having a selector name that is misleading.
I think that we should probably update the "Workload Selectors" table as well, with a value for image_id
more like an image name instead of a digest, and also the description.
There are a couple of changes that we should also make to make the linter happy.
Thank you very much for this contribution!
-selector docker:image_id:envoyproxy/envoy:contrib-v1.29.1 | ||
``` | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line should be removed.
ghcr.io/spiffe/spire-server 1.9.1 e3b24c3cd9e1 4 weeks ago 103MB | ||
envoyproxy/envoy contrib-v1.29.1 644f45f6626c 7 weeks ago 181MB | ||
``` | ||
Then use the `REPOSITORY:TAG` as the selector, not the `IMAGE ID` column. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There should be a new line before this text starts.
Hello @amartinezfayo, I apologize for the delay in implementing the required fixes, I've been immersed in my bachelor's thesis (which is about access control of Kafka using SPIRE!!). |
@raissonsouto No worries! |
Hey @raissonsouto, we still need to have DCO fixed in order to be able to merge this. Could you address that? |
Hi @raissonsouto, quick reminder that we need to have DCO fixed to be able to merge this contribution. |
…ontribution Signed-off-by: Agustín Martínez Fayó <amartinezfayo@gmail.com>
@raissonsouto Since we still have the DCO missing in this PR, I've opened #5220 taking this contribution so we can get it merged. I'm closing this PR in favor of #5220. Thanks again! |
…ution (#5220) Signed-off-by: Agustín Martínez Fayó <amartinezfayo@gmail.com>
Affected functionality
None.
Description of change
Improving documentation of the Docker workload attestor.