Skip to content
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

qm container: force use iptables-nft and avoid iptables-legacy #267

Closed
dougsland opened this issue Nov 2, 2023 · 2 comments
Closed

qm container: force use iptables-nft and avoid iptables-legacy #267

dougsland opened this issue Nov 2, 2023 · 2 comments

Comments

@dougsland
Copy link
Collaborator

RHEL kernel only support iptables-nft, we need to make sure in the container you also have iptables-nft installed

bash-5.1# rpm -qa | grep -i iptables
iptables-legacy-libs-1.8.8-6.el9.2.x86_64
iptables-libs-1.8.8-6.el9.x86_64
iptables-legacy-1.8.8-6.el9.2.x86_64

avoid such error when creating a container with podman:

Error: netavark: code: 3, msg: modprobe: FATAL: Module ip_tables not found in directory /lib/modules/5.14.0-370.331.el9iv.aarch64
iptables v1.8.8 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
@Yarboa
Copy link
Collaborator

Yarboa commented Nov 7, 2023

@dougsland
Isnt it resolved by this? #268

@dougsland
Copy link
Collaborator Author

@Yarboa yes, thanks for the heads up!
Resolved!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants