New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting a MTU for dind is difficult #103
Comments
Try this: https://hub.docker.com/r/lordgaav/dind-options/ Worked for me by setting DOCKER_OPTS: "--insecure-registry [snip] --mtu=1400" in my .gitlab-ci.yml, apologies if I misunderstood and this doesn't help :) |
Duplicate of #102. As a side note, you can specify |
useful trick thanks. #102 is closed(and I can't re-open it) so is it safe to assume the docker image isn't going to add a specific fix for this? |
Is there something that we can do in the image? From #102 I had assumed that it was not something that could be fixed in the image. Not sure why you can't re-open your own issue that you closed. |
oh you're right because I closed it. I don't github much and have never been able to re-open an issue before. I don't know what was happening over there but I think it was a combination of it being hard to set for the container and some weird behaviors in how docker handles mtu. I assume its possible to do |
After some tentative ( "I became mad about it" ), I figured out how to do it. Though this is referred in multiple locations I could not find a a clear explanation.
To
To test it inside the Gitlab container you should get:
I was mislead from the Gitlab documentation where the example show only the first version. |
There is a big need for it: Being able to globally configure this with env variables in Gitlab CI so that not every project needs to adjust their gitlab-ci.yaml with the setup described by @zioalex |
moby/moby#36659 isn't fixed for me yet, but assuming at some point it is setting the MTU is currently a bit tricky for the dind image in certain scenarios.
In my case I want to run dind as a service to GitLab CI builds running in Kubernetes. For that to work I need to control the MTU of the docker bridge and I have limited control of how the service is started. Basically only really able to specify environment and and image (not able to interact with entrypoint).
I think I have 2 options.
If 2, I'm willing to do the work writing and testing a PR given some direction on what sort of approach would be ideal. Or just testing someone else's PR. :-D
The text was updated successfully, but these errors were encountered: