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

Use nftables instead of the deprecated iptables #934

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

NeroReflex
Copy link
Contributor

@NeroReflex NeroReflex commented Apr 11, 2024

As per title: use iptables-nft instead of the deprecated iptables.

See https://gitlab.archlinux.org/archlinux/packaging/packages/iptables/-/issues/1 for more details.

The deprecated iptables is not completely suitable for docker or podman as stated in that page.

The reason this is not in PACKAGES is the following error will appear:

error: unresolvable package conflicts detected
:: iptables-nft-1:1.8.10-1 and iptables-1:1.8.10-1 are in conflict. Remove iptables? [y/N] 
:: iptables-nft-1:1.8.10-1 and iptables-1:1.8.10-1 are in conflict
error: failed to prepare transaction (conflicting dependencies)

@NeroReflex NeroReflex marked this pull request as ready for review April 12, 2024 00:28
@pastaq
Copy link
Contributor

pastaq commented Apr 13, 2024

LGTM

@NeroReflex
Copy link
Contributor Author

@pastaq I spotted a problem: it forces the pacman database to be regenerated. That has to be moved to solve this, or the install must be moved early in the build process....

@pastaq
Copy link
Contributor

pastaq commented Apr 22, 2024

The reason this is not in PACKAGES is the following error will appear:

error: unresolvable package conflicts detected
:: iptables-nft-1:1.8.10-1 and iptables-1:1.8.10-1 are in conflict. Remove iptables? [y/N] 
:: iptables-nft-1:1.8.10-1 and iptables-1:1.8.10-1 are in conflict
error: failed to prepare transaction (conflicting dependencies)

The base meta package has iptables as a dependency and it doesn't reflect iptables-nft as a suitable replacement for some reason.

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

Successfully merging this pull request may close these issues.

None yet

2 participants