Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-32374

[podman5.1] Can't run a container due to issues with firewall rule insertion

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • rhel-10.0.beta
    • rhel-10.0.beta
    • podman
    • None
    • None
    • Important
    • 5
    • rhel-container-tools
    • 3
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • RUN 252, RUN 253, RUN 254, RUN 255, RUN 256
    • None

      What were you trying to do that didn't work?

      Running a container on RHEL-10.0-20240318.5 fails, as apparently it's not possible to create a necessary firewall rule:
      # podman run -it registry.access.redhat.com/ubi9/ubi:latest
      Error: netavark: unable to append rule '! -d 224.0.0.0/4 -j MASQUERADE' to table 'nat': code: 4, msg: Warning: Extension MASQUERADE revision 0 not supported, missing kernel module?
      iptables v1.8.10 (nf_tables): RULE_APPEND failed (No such file or directory): rule in chain NETAVARK-1D8721804F16F

      Please provide the package NVR for which bug is seen:

      podman-5.0.0~rc1-3.el10.x86_64
      netavark-1.10.3-1.el10.x86_64

      How reproducible:

      Always.

      Steps to reproduce

      1. Install podman and pull some container image.
      2. Run a container using the image, e. g. podman run -it registry.access.redhat.com/ubi9/ubi:latest

      Expected results

      Podman runs the container, firewall configuration is successful.

      Actual results

      Container can't be run due to issue with firewall rule insertion.

      Additional notes

      I was able to solve the issue in two ways:
      1. install kernel-modules-extra package and modprobe nft_compat module;
      2. define a nftables firewall driver in /etc/containers/containers.conf:
      [network]
      firewall_driver="nftables"

      I can't judge what should be the proper default solution, but I think there could be either some autodetection mechanism (to account for situations where the system is configured with firewalld, or with just nftables), or some sane default with appropriate documentation covering non-standard firewall configurations.

              container-runtime-eng Container Runtime Eng Bot
              rhn-support-jikortus Jiri Kortus
              Container Runtime Eng Bot Container Runtime Eng Bot
              Yuhui Jiang Yuhui Jiang
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: