-
Notifications
You must be signed in to change notification settings - Fork 34
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
Running the action in a container fails #44
Comments
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. apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
name: ghe-runnerdeploy
spec:
replicas: 1
template:
spec:
repository: oguzhan/dummy
containers:
- name: runner
securityContext:
privileged: true
volumeMounts:
- name: debugfs
mountPath: /sys/kernel/debug
volumes:
- name: debugfs
hostPath:
path: /sys/kernel/debug
type: DirectoryOrCreate Also, just an FYI about the current status of Thundra and its products: https://www.catchpoint.com/press-releases/catchpoint-invests-to-advance-api-cloud-functions-and-microservices-monitoring |
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: