actions/runner-container-hooks
1
0
Fork 0
mirror of https://github.com/actions/runner-container-hooks.git synced 2025-12-15 01:06:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat: check if required binaries are present (#272)

Browse Source 
* feat: check if required binaries are present

Previously the necessary binaries were copied over using the runner
container. This lead to issues in case your main container was using the
musl libc implementation.

Instead of copying over any binaries, the initContainer now checks if
the required binaries are present in the main container.

* feat: get rid of the init container

* fix: add _runner_file_commands

* fix: do not fail if _runner_file_commands does not exist

It seems that for container actions this directory does not exist.
This commit is contained in:
vvanouytsel-trendminer
2025-11-10 15:01:40 +01:00
committed by GitHub
parent 2934de33f8
commit ad9cb43c31
4 changed files with 4 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
packages/k8s/README.md
View File

@@ -41,3 +41,4 @@ rules:
- Container actions will not have access to the services network or job container network
- Docker [create options](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idcontaineroptions) are not supported
- Container actions will have to specify the entrypoint, since the default entrypoint will be overridden to run the commands from the workflow.
- Container actions need to have the following binaries in their container image: `sh`, `env`, `tail`.