-
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
failed to create bridge "cni-podman0" when trying to start a container #4114
Comments
just to be sure, what version of the containernetworking-plugins do you have installed? |
Thanks for your reply! I'm not so sure about cni plugin version. All I know is the k8s version is 1.13.1, bootstraped with hyperkube the |
The cni-plugin version is |
@LeoQuote can you paste in the contents of the 87-podman ... file ? |
Sure , it’s copied from project example https://github.com/containers/libpod/blob/d76b21e27a7cef26865a05be02632ca76f9cf2ea/cni/87-podman-bridge.conflist |
that file recently changed, which is why I asked. I wanted to make double sure yours has the updated file. |
Thanks for your patience 😂 Here’s the full conflist file:
——— |
I found the problem, we're using this node as k8s node at the same time, the calico-node overwrited cni bin files during setup, I fix it by reinstalling cni-plugin. closing the issue |
Unfortunately I found |
I added cni-podman0 bridge manually and finally fixed it, perhaps we can add this to document?
|
@LeoQuote Care to open a PR to fix the documentation, or at least document the steps you went through? |
I view this as a CNI bug; we should never require manual intervention in bridge creation. |
I'm hitting this today when running podman as root |
This issue had no activity for 30 days. In the absence of activity or the "do-not-close" label, the issue will be automatically closed within 7 days. |
Friendly ping. |
Has an issue been opened on CNI? |
Opened this as a CNI issue containernetworking/cni#770 |
Try cni-plugins-0.8.6 (gentoo ebuilds now require it). |
@zmedico this issue didnt show up since then, we're now using Really appreciate your help! |
closinig as this sounds fixed or distribution specific |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
podman run docker.io/busybox
Describe the results you received:
container failed to start
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
I used the exact configure file as https://github.com/containers/libpod/blob/master/cni/87-podman-bridge.conflist
the log in
everything
could be helpful ?I've checked the network as the document in https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#network-plugin-requirements
the
net/bridge/bridge-nf-call-iptables
is already set to 1.How can I troubleshoot this problem now?
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
physical
The cni-plugin version is
0.8.1
The text was updated successfully, but these errors were encountered: