Fix Job container MTU: use bridge network instead of per-job network
CI - Lint & Test / lint-and-test (push) Failing after 0s
Details
CI - Lint & Test / lint-and-test (push) Failing after 0s
Details
act_runner creates a custom Docker network per job which doesn't inherit the --mtu=1340 setting. Using the default bridge network ensures job containers use the correct MTU matching pod network. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
86e92016e0
commit
e9fb0566b0
|
|
@ -25,7 +25,7 @@ data:
|
||||||
- "ubuntu-22.04:docker://catthehacker/ubuntu:act-22.04"
|
- "ubuntu-22.04:docker://catthehacker/ubuntu:act-22.04"
|
||||||
- "self-hosted:host"
|
- "self-hosted:host"
|
||||||
container:
|
container:
|
||||||
network: ""
|
network: "bridge"
|
||||||
privileged: false
|
privileged: false
|
||||||
options:
|
options:
|
||||||
valid_volumes: []
|
valid_volumes: []
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue