-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-9.0.0
-
None
-
Moderate
-
1
-
rhel-sst-container-tools
-
3
-
False
-
-
None
-
RUN 252
-
If docs needed, set a value
-
-
Unspecified
-
None
Description of problem:
When running a container via podman, the following errors are logged to dmesg and pop up on the console:
[ 30.648852] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 30.662142] IPv6: ADDRCONF(NETDEV_CHANGE): vethd6d8e018: link becomes ready
[ 30.662202] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 30.662447] cni-podman0: port 1(vethd6d8e018) entered blocking state
[ 30.662470] cni-podman0: port 1(vethd6d8e018) entered disabled state
[ 30.662535] device vethd6d8e018 entered promiscuous mode
[ 30.662612] cni-podman0: port 1(vethd6d8e018) entered blocking state
[ 30.662633] cni-podman0: port 1(vethd6d8e018) entered forwarding state
[ 30.683316] Warning: Deprecated Driver is detected: nft_compat will not be maintained in a future major release and may be disabled
[ 36.217706] cni-podman0: port 1(vethd6d8e018) entered disabled state
[ 36.217967] device vethd6d8e018 left promiscuous mode
[ 36.217984] cni-podman0: port 1(vethd6d8e018) entered disabled state
[root@localhost ~]#
Version-Release number of selected component (if applicable):
podman-4.0.2-6.el9_0.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Install RHEL 9 and podman
2. Run a container
3. Check dmesg for the deprecated messages
Actual results:
Things work fine, but using deprecated functionality
Expected results:
Latest podman uses fully supported functionality
Additional info:
- external trackers
- links to
-
RHSA-2023:123943 podman bug fix and enhancement update