Allow to specify docker network options, such as mtu
See original GitHub issueDescribe the enhancement
It would be great to set up custom options for networks created for container
jobs.
As of now, it is only possible to pass options to docker create
command via jobs.<job_id>.container.options
Code Snippet This could look this way:
container:
image: centos:7
network:
options:
mtu: 1400
Additional information
See, according to https://github.com/moby/moby/issues/34981 , docker daemon options, such as mtu, are not passed to new bridge networks. So my CI jobs fail while trying to e. g. run yum -y update
.
NOTE: if the feature request has been agreed upon then the assignee will create an ADR. See docs/adrs/README.md
Issue Analytics
- State:
- Created 3 years ago
- Reactions:22
- Comments:9
Top Results From Across the Web
docker network create
If you want to create an externally isolated overlay network, you can specify the --internal option.
Read more >Docker MTU issues and solutions - Matthias Lohr
I like this solution because the default MTU of 1500 can stay in place for the default bridge network and for the bridges...
Read more >Fixing Docker's MTU Issues on Ubuntu
Learn how to optimize Docker's MTU settings to prevent connectivity issues and enhance your Docker experience, especially on Ubuntu systems.
Read more >How we spent a full day figuring out a MTU issue with docker
I decided to change the network mode of my container. Instead of bridge which is the default network mode, I tried the host...
Read more >Understanding Docker's -net=host Option
In this post we will learn briefly about various networking modes available for Docker containers and deep dive into Host Mode networking.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Instead of applying all these hacks and using non-official container image (although thanks for making that available @tiagoblackcode), can we get this fixed in the runner itself? Seems like it comes down to checking the MTU from the network bridge and using that when creating the network.
https://github.com/actions-runner-controller/actions-runner-controller/issues/1046#issuecomment-1041354554
Hello @sharonovd … The lack of possibility to set MTU has bit me hard the past few days. Is there any progress on this front? Any workarounds available today to pass custom options at the
docker network create
step ? Thanks!