-
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
CNI: failed to set bridge addr: "cni-podman1" already has an IP address different from 10.25.31.1/24 #12306
Comments
I renamed the issue to display the correct issue |
OK I took a look at the logs. I think the actual issue is @edsantiago Can you grep for |
Here are some. They seem to begin on 11-09. Podman network connect and disconnect [It] podman network disconnect and run with network ID
|
#12183 caused this, I know how to fix it. I will open a PR later this week. |
The netns cleanup code is checking if there are running containers, this can fail if you run several libpod instances with diffrent root/runroot. To fix it we use one netns for each libpod instances. To prevent name conflicts we use a hash from the static dir as part of the name. Previously this worked because we would use the CNI files to check if the netns was still in use. but this is no longer possible with netavark. [NO NEW TESTS NEEDED] Fixes containers#12306 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
New flake in the
podman play kube --ip and --mac-address
test:Podman play kube [It] podman play kube --ip and --mac-address
Also seen just now in a live PR, in f34 rootless
The text was updated successfully, but these errors were encountered: