Tiago Melo

Hello, I've come across this issue as well since the Kubernetes network I'm setting up uses a smaller MTU (1420 instead of the usual 1500). Despite the MTU being configurable...

I agree with the general sentiment that the issue is not in ARC but instead in `actions/runner` or even in docker, honestly. Since docker supports the `--mtu` flag, it should...

I'm willing to help you with support. I'm gonna prepare a PR with the secondary image and regarding it in the next couple of days.

Hello, I finally had some time to work on this. Please check out #1201 which adds a new docker image to the repository that propagates the MTU setting to networks...

This is done on a separate image because there might be some unintended consequences of using a shell script instead of the original docker binary. The shell script is required...

I'm not sure I'm following, but I don't think we should have a customisation specifically for a cloud provider. There are situations where the MTU can stay at 1500 and...

I'm okay with using the official image and wrapping the docker binary with the shell script. Should we wait until the docker binary is moved to `/usr/bin` as suggested by...

Updated the PR with the changes. Haven't had the chance to test it properly yet, but it's still missing the flag to enable the MTU propagation. @Fleshgrinder in your shell...

Wouldn't it be better to have a configuration on the `Runner` CRD along with `dockerMTU` called `dockerMTUPropagation`? e.g. ``` --- apiVersion: actions.summerwind.dev/v1alpha1 kind: Runner spec: dockerMTU: 1420 dockerMTUPropagation: true ```...

I understand, but in terms of API I'd rather configure the runner using spec than an environment variable. I'll wait for @mumoshu 's input before committing to a solution. Thanks...