-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
podman network create: add option to set custom network driver settings, eg like MTU #8454
Comments
@pschiffe interested in opening a PR to fix this? |
This would be useful for minikube as well, I can probably do a PR for it |
You got it. |
Most likely it will be a simple option to "network create", rather than -o com.docker.network.driver.mtu=1500 But I suppose it could eventually be some kind of passthrough to the CNI parameters, not current code though |
Seems to be working:
27: cni-podman1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 29: cni-podman2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 5000 qdisc noqueue state UP group default qlen 1000 |
Looking great and good enough for me, thank you! |
Syntax now changed to:
Resulting configuration diff: @@ -1,12 +1,13 @@
{
"cniVersion": "0.4.0",
- "name": "podman1",
+ "name": "podman2",
"plugins": [
{
"type": "bridge",
- "bridge": "cni-podman1",
+ "bridge": "cni-podman2",
"isGateway": true,
"ipMasq": true,
+ "mtu": 5000,
"hairpinMode": true,
"ipam": {
"type": "host-local",
@@ -18,7 +19,7 @@
"ranges": [
[
{
- "subnet": "10.89.0.0/24"
+ "subnet": "10.89.1.0/24"
}
]
]
|
Resolved via #8457 |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
Docker command
docker network create
has the-o, --opt map Set driver specific options (default map[])
option.With podman, one have to modify the config file in
/etc/cni/
once the network is created to change its settings, which is not very automation friendly.Related ansible collection RFE: containers/ansible-podman-collections#147
The text was updated successfully, but these errors were encountered: