fix(kubernetes): also set DinD MTU on user-defined networks #51
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/dind-mtu-match-pod-network"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
--mtu only applies to the default bridge (docker0). act_runner runs each
job on a per-job user-defined network, and those default to 1500
regardless of --mtu -- so jobs still emitted oversized frames and large
downloads still stalled even after docker0 was corrected to the pod MTU.
Also pass --default-network-opt bridge=com.docker.network.driver.mtu=$mtu
so every bridge network the daemon creates inherits the matched MTU.
Verified in a runner's dind: a fresh user network's container now comes up
at 1450 instead of 1500.
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com
Automated review by pr-reviewer v0.32.2 | Safety Check | Mistral Small | tracking id
r-5d746e-d63aa7This is an AI-genrated review and may contain mistakes.
Status: ⚠️ Unavailable
Review unavailable — the inference service isn't reachable right now. This isn't a problem with your PR. Tracking id
r-5d746e-d63aa7.Comment
@pr-reviewer-bot retryonce it's back.dd9940ef0fe62fb794fdAutomated review by pr-reviewer v0.32.2 | Safety Check | Mistral Small | tracking id
r-5d7476-fcf73cThis is an AI-generated review and may contain mistakes.
Status: ⚠️ Unavailable
Review unavailable — the inference service isn't reachable right now. This isn't a problem with your PR. Tracking id
r-5d7476-fcf73c.Comment
@pr-reviewer-bot retryonce it's back.