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 1414436 - Restart policy on-failure does not start container after boot
Summary: Restart policy on-failure does not start container after boot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Daniel Walsh
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On: 1413954
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-18 13:55 UTC by Antonio Murdaca
Modified: 2019-03-06 00:35 UTC (History)
16 users (show)

Fixed In Version: docker-1.12.6-1.el7_3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1413954
Environment:
Last Closed: 2017-03-02 19:08:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0406 0 normal SHIPPED_LIVE docker bug fix and enhancement update 2017-03-03 00:06:50 UTC

Comment 1 Antonio Murdaca 2017-01-18 13:55:56 UTC 
Fixed in docker-1.12.6 (if we might going to rebuild for RHEL)
Comment 2 Daniel Walsh 2017-01-18 15:00:05 UTC 
Will have to wait for the next release.
Comment 5 Luwen Su 2017-02-19 18:31:31 UTC 
In docker-1.12.6-6.el7.x86_64, works fine.

c3f580983ba7        docker.io/registry   "/entrypoint.sh /etc/"   About a minute ago   Up Less than a second   0.0.0.0:5555->5000/tcp   registry_on_failure
b1829c4be873        docker.io/registry   "/entrypoint.sh /etc/"   About a minute ago   Up Less than a second   0.0.0.0:5000->5000/tcp   registry_always


Move to verified.
Comment 7 errata-xmlrpc 2017-03-02 19:08:37 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-2017-0406.html
Note You need to log in before you can comment on or make changes to this bug.