Initialize container manager based on whether the ContainerHooksPath is set #2317
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the operation provider is called, it initializes both the dockerManager and the containerHookManager.
The dockerManager will call
which
on docker, which can cause initialization to fail.The fix should relax the docker cli dependency if the runner is going to use container hooks.
Related to the issue in runner-container-hooks: actions/runner-container-hooks#30