RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1279015 - Docker 1.8.2 fails to set iptables rules
Summary: Docker 1.8.2 fails to set iptables rules
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: smahajan@redhat.com
QA Contact: atomic-bugs@redhat.com
URL: https://github.com/docker/docker/pull...
Whiteboard:
Depends On: 1279002
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-07 06:22 UTC by Daniel Walsh
Modified: 2019-03-06 00:37 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1279002
Environment:
Last Closed: 2016-03-31 23:22:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0536 0 normal SHIPPED_LIVE docker bug fix and enhancement update 2016-04-01 03:19:56 UTC

Comment 2 Daniel Walsh 2015-11-07 06:27:55 UTC 
Shishir we need to back port the fix for this, if we don't have it currently.
Comment 3 Daniel Walsh 2015-12-01 19:28:07 UTC 
Fixed in docker-1.9
Comment 5 Luwen Su 2016-03-17 19:23:19 UTC 
Hi,

I still get the firewalld's noisy in docker-1.9.1-23.el7.x86_64, just install and start the docker.service,

any suggestion  to debug with it? 

Other packages:
firewalld-0.3.9-14.el7.noarch
iptables-1.4.21-16.el7.x86_64

2016-03-18 03:18:59 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -t nat -C POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE' failed: iptables: No chain/target/match by that name.
Mar 18 03:18:59 timesu.com firewalld[32368]: 2016-03-18 03:18:59 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -D FORWARD -i docker0 -o docker0 -j DROP' failed: iptables: Bad rule (does a matching rule exist in that chain?).
Mar 18 03:18:59 timesu.com firewalld[32368]: 2016-03-18 03:18:59 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -t filter -C FORWARD -i docker0 -o docker0 -j ACCEPT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
Mar 18 03:18:59 timesu.com firewalld[32368]: 2016-03-18 03:18:59 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -t filter -C FORWARD -i docker0 ! -o docker0 -j ACCEPT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
Mar 18 03:18:59 timesu.com firewalld[32368]: 2016-03-18 03:18:59 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -t filter -C FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
Mar 18 03:18:59 timesu.com firewalld[32368]: 2016-03-18 03:18:59 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -t nat -C PREROUTING -m addrtype --dst-type LOCAL -j DOCKER' failed: iptables v1.4.21: Couldn't load target `DOCKER':No such file or directory
                                             
                                             Try `iptables -h' or 'iptables --help' for more information.
Mar 18 03:18:59 timesu.com firewalld[32368]: 2016-03-18 03:18:59 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER' failed: iptables v1.4.21: Couldn't load target `DOCKER':No such file or directory
                                             
                                             Try `iptables -h' or 'iptables --help' for more information.
Comment 6 Daniel Walsh 2016-03-17 19:30:31 UTC 
There is nothing to debug here.  This is just the way docker works. Docker sends a message to firewalld to remove all records for DOCKER, and then adds rules for it.  Since DOCKER does not exist when it runs, firewalld reports no rules exist.  Sadly their is no rm -f foobar, where we could tell firewalld remove this rules if they exist and don't complain if they do not.
Comment 7 Luwen Su 2016-03-20 13:15:13 UTC 
Okay, thus then i'd like to move this to verified.
Comment 9 errata-xmlrpc 2016-03-31 23:22:57 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0536.html
Note You need to log in before you can comment on or make changes to this bug.