e7a21cfc53
* feat: Add container to propagate host network MTU Some network environments use non-standard MTU values. In these situations, the `DockerMTU` setting might be used to specify the MTU setting for the `bridge` network created by Docker. However, when the Github Actions workflow creates networks, it doesn't propagate the `bridge` network MTU which can lead to `connection reset by peer` messages. To overcome this, I've created a new docker image called `summerwind/actions-runner-mtu` that shims the docker binary in order to propagate the MTU setting to networks created by Github workflows. This is a follow-up on the discussion in (#1046)[https://github.com/actions-runner-controller/actions-runner-controller/issues/1046] and uses a separate image since there might be some unintended side-effects with this approach. * fixup! feat: Add container to propagate host network MTU Co-authored-by: Yusuke Kuoka <ykuoka@gmail.com> |
||
|---|---|---|
| .. | ||
| hooks | ||
| supervisor | ||
| .dockerignore | ||
| Makefile | ||
| actions-runner-dind-rootless.dockerfile | ||
| actions-runner-dind.dockerfile | ||
| actions-runner.dockerfile | ||
| docker-shim.sh | ||
| entrypoint.sh | ||
| logger.bash | ||
| rootless-startup.sh | ||
| startup.sh | ||
| update-status | ||