-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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 errors using CNI on Risc-V archtecture #3462
Comments
could you try without |
When I reverted the iptables to legacy (on Debian), it worked but printed tons of messages to dmesg.
Dmesg output:
Both VMs, Debian and Fedora uses exactly the same Kernel and modules but on Fedora (that iptables show as legacy) I get the error. My Kernel config is on https://gist.github.com/carlosedp/4100815296675d126334f8f6afba4e93. |
@dcbw do you know what could be causing this issue? |
After rebuilding the plugins from https://github.com/containernetworking/plugins and placing them on |
After all work by @giuseppe towards having Podman on Risc-V architecture, everything works fine (building, running, etc) containers but I'm seeing some problems with CNI (not using
--net host
).On Fedora VM:
Starting a podman container with CNI gives:
After this, deleting and starting a new container with host network, the container doesn't give an error but the application becomes unaccessible until reboot.
With host network (
--net host
), it works (start, stop, delete).On Debian VM:
Container starts and runs with CNI but shows error when deleting.
After this, even starting a new container with host network, the application becomes unaccessible until reboot.
Its port only gets ipv6 stack:
Let me know how can I further help debugging this. There is a Debian VM available for download here in case needed.
The text was updated successfully, but these errors were encountered: