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
{{ message }}
Repository navigation
Container Hooks does not implement the -docker- variants, and this prevents customizing network name #4764
The runner image has its own hook implementation, that is different to the runner-container-hooks docker implementation. This prevents using ACTIONS_RUNNER_NETWORK_DRIVER.
Adding the following would provide the docker-hooks directly in the default runner.
Is this an intentional decision to remove it? Are we meant to provide this ourselves? Because the default image does copy over the k8s and k8s-novolume versions of the container hooks
To Reproduce
Create a runner with ACTIONS_RUNNER_NETWORK_DRIVER=host
Activity