Bug 1932157 - Update F33 iptables to >= v1.8.6
Summary: Update F33 iptables to >= v1.8.6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: iptables
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Phil Sutter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-24 05:41 UTC by Akihiro Suda
Modified: 2021-03-28 17:24 UTC (History)
3 users (show)

Fixed In Version: iptables-1.8.5-6.fc33
Clone Of:
Environment:
Last Closed: 2021-03-28 17:24:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Akihiro Suda 2021-02-24 05:41:22 UTC
Please consider updating iptables package of Fedora 33 (currently v1.3.5) to v1.3.6 or later, so as to include commit "iptables: accept lock file name at runtime": https://git.netfilter.org/iptables/commit/?id=5105e844c2ff6a3e320bf8cdadc5094d4eaef2b7

If updating the entire package is problematic, just cherry-picking the commit mentioned above would be fine.

The commit is needed for running Rootless Docker on SELinux-enabled hosts: https://github.com/moby/moby/issues/41230#issuecomment-783076135

Comment 1 Fedora Update System 2021-03-24 15:48:38 UTC
FEDORA-2021-4d9a2dad72 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4d9a2dad72

Comment 2 Fedora Update System 2021-03-25 01:32:16 UTC
FEDORA-2021-4d9a2dad72 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4d9a2dad72`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4d9a2dad72

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2021-03-28 17:24:43 UTC
FEDORA-2021-4d9a2dad72 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.