actions / actions/runner-container-hooks
Non-existing systemMount folders prevent use of podman
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 153
- Forks
- 112
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
I am trying to create podman hooks. When I log the json github sends, it includes some system mounts for folders that do not exist on my runner.
{
"userProvidedValue": null,
"sourceVolumePath": "/root/actions-runner/_work/_actions",
"targetVolumePath": "/__w/_actions",
"readOnly": false
},
I believe this works on docker because docker will automatically creating missing mounts on your host. Podman errors on missing dirs https://github.com/containers/podman/issues/6234 Error: statfs /root/actions-runner/_work/_actions: no such file or directory. I tried creating these dirs by hand, but something about the github runner deletes them.
I suppose this is sort of a runner bug moreso than a hook bug, but it's kind of cross-cutting.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by reproducing the Podman failure with the logged systemMount paths and trace how the runner container hook prepares those mounts; done means missing source directories no longer prevent the hook from running with Podman.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100