Skip to content

Conversation

@l0rd
Copy link
Member

@l0rd l0rd commented Nov 19, 2025

Podman 6.0 no longer supports iptables. It's a good opportunity to remove iptables from machine-os too.

This is a follow-up of

And related to https://issues.redhat.com/browse/RUN-3723

We should wait for containers/podman#27555 to be merged before merging this one (WSL machine e2e tests as currently configured to use iptables).

Removed iptables package and kernel modules

Podman 6.0 won't support iptables anymore. It's a
good opportunity to remove iptables from machine-os
too.

This is a follow-up of

containers/netavark#1353
containers/podman#27555

and related to

https://issues.redhat.com/browse/RUN-3723

Signed-off-by: Mario Loriedo <[email protected]>
@openshift-ci
Copy link

openshift-ci bot commented Nov 19, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: l0rd

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Luap99
Copy link
Member

Luap99 commented Nov 20, 2025

Note this here was never added for WSL but rather because end users wnated to use iptables inside the containers and without the nodule being loaded on the host that won't work, containers/podman#25153

I don't mind the removal per se, I think 6.0 is a good timing but maybe we should try to find out if users still need it.
docker 29 finally added nftables support but it is still experimental so who knows how long they keep the iptables stuff around.

Overall this "costs" us nothing to keep as long as fedora keeps building kernels with these modules so if we know of users I think keeping this is best. @ankudinov you reported the original issue, do you still require iptables support inside the containers?

@ankudinov
Copy link

@Luap99 and @l0rd If this "cost nothing", I'd appreciate if we keep legacy iptables. The reality is complex and not every container running on Podman will be up to date. Our use case is running containerized network OS (Arista cEOS-lab) which was heavily relying on iptables until recently, while we have ongoing work to switch to nftables and recent images should be fine, we still have plenty of legacy images in the field. Also lab / dev environments can bring a lot of surprises.
Eventually iptables must be removed. But a good long grace period helps a lot.

@Luap99 Thank you for asking. One reason I love Podman so much is that I can always tell a network engineer (that knows nothing about the kernel) - Podman just works! And avoid building custom machine. You are the best guys!

@l0rd
Copy link
Member Author

l0rd commented Nov 21, 2025

Thank you @ankudinov for your feedback. Let me close this PR then.

@l0rd l0rd closed this Nov 21, 2025
openssh-server
cifs-utils
nfs-utils-coreos
iptables-nft
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can still remove this package install though. If people are using it inside the container they won't need the package on the host.

Comment on lines -8 to -9
# TODO (6.0): consider removing this in a major release where we can justify
# removing legacy modules.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might want to update the comment then, maybe just link to my comment on the PR.

@l0rd
Copy link
Member Author

l0rd commented Nov 21, 2025

Ok, PR updated and reopened. With only the package removed and the comment updated.

@l0rd l0rd changed the title Remove iptables package and kernel modules Remove iptables package Nov 21, 2025
@l0rd
Copy link
Member Author

l0rd commented Nov 21, 2025

GitHub doesn't let me reopen the PR because I force-pushed the branch while it was closed.
The new PR: #199

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants