Open bschilder opened 8 months ago
Hey @bschilder, thank you for raising an issue.
At a glance, the workflow with the problem seems to be using a container to run the job. Since the workflow-telemetry-action uses an eBPF program (called proc_tracer_ubuntu-22
in this case) and it would have to be run with sudo
, it would need security privileges to run in a container.
As you pointed out (#44), the solution would be to run the container with privileged: true
and mount the debugfs
syscalls, since it probably won't be available within a container by default.
It does look like GitHub Action allows these to be set in the jobs.<job_id>.container.options
. See: https://docs.github.com/en/actions/using-jobs/running-jobs-in-a-container#setting-container-resource-options
Hope this clarifies some things and helps you resolve the issue.
Bests.
Thanks so much for the rapid and helpful reply! I'll try this out and let you know how it goes!
Hi @bschilder,
Had you a chance to try solution suggested by @rwxdash?
Hi there, thanks for the awesome action! I'm currently using it as part of the rworkfows action and one of my users reported an error.
Any insights you might be able to provide would be greatly appreciated! @rwxdash @suleymanbarman
1. Bug description
An error arises during the telemetry step in the rworkflows action.
Console output
https://github.com/tempbioc/parody/actions/runs/7700556648/job/20984649706
Expected behaviour
Telemetry actions runs all the way through and produces reports.
2. Reproducible example
https://github.com/tempbioc/parody/actions/runs/7700556648/workflow
Potentially related issues