You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any chance this action could run inside of a container? I tried to run this inside of a Ubuntu 22.04 container and it fails. I love the information it returns and that it runs across all types of hosted runners.
At work we use the actions-runner-controller, which means all runners are hosted inside of containers with docker-in-docker capabilities. I suspect it will fail there as well, but have not tested yet. I would really like to suggest this action to our users for helping them right sizing the runners they use.
The text was updated successfully, but these errors were encountered:
Yes, it's possible to run this in a container. If I recall correctly, you would need to set the privileged mode to true when running it. However, eBPF calls should be available in order to run successfully. Not sure of the exact configuration for a stand-alone container setup, but for the actions-runner-controller we've used the following configuration to make the functionality available. This was for some time ago, so again, I'm not certain if it still works but the idea is the same; make it privileged and make the eBPF syscalls available inside the container.
Any chance this action could run inside of a container? I tried to run this inside of a Ubuntu 22.04 container and it fails. I love the information it returns and that it runs across all types of hosted runners.
At work we use the actions-runner-controller, which means all runners are hosted inside of containers with docker-in-docker capabilities. I suspect it will fail there as well, but have not tested yet. I would really like to suggest this action to our users for helping them right sizing the runners they use.
The text was updated successfully, but these errors were encountered: