-
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 4.0.2 with docker-compose 2.6.0 does not update network MTU (rootful) #14482
Comments
Can you get a |
It is in the original post under "Describe the results you received" |
@jakecorrenti This looks like a good bug to look at next |
Previously, the following network block did not update using docker-compose: ``` networks: default: driver: bridge driver_opts: mtu: 9000 ``` In the API, the network options were previously not being handled when the network was being created. I translated the docker options into podman options, and added the options to the network. When doing `podman network inspect <network>`, the results now contain `"mtu": "9000"` Fixes: containers#14482 Signed-off-by: Jake Correnti <[email protected]>
A friendly reminder that this issue had no activity for 30 days. |
@jakecorrenti Still working on this? |
Looks like some 2 failing tests that I lost track of. I'll get that going green today. |
Previously, the following network block did not update using docker-compose: ``` networks: default: driver: bridge driver_opts: mtu: 9000 ``` In the API, the network options were previously not being handled when the network was being created. I translated the docker options into podman options, and added the options to the network. When doing `podman network inspect <network>`, the results now contain `"mtu": "9000"` Fixes: containers#14482 Signed-off-by: Jake Correnti <[email protected]>
/kind bug
Description
The following network block does not update using docker-compose
Steps to reproduce the issue:
vi docker-compose.yml
docker-compose up -d
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Tested on multiple versions (up to 4.0.2)
Tested on multiple systems (all 10Gbps capable)
Output of
podman version
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes (latest available version of podman for RHEL 8)
The text was updated successfully, but these errors were encountered: