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 1365207 - [extras-rhel-7.2.7] docker daemon fails to start: "/usr/bin/dockerd-latest" requires 0 arguments
Summary: [extras-rhel-7.2.7] docker daemon fails to start: "/usr/bin/dockerd-latest" r...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker-latest
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-08 15:35 UTC by Ed Santiago
Modified: 2016-09-15 08:29 UTC (History)
1 user (show)

Fixed In Version: docker-latest-1.12.0-4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-15 08:29:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1829 0 normal SHIPPED_LIVE docker-latest bug fix and enhancement update 2016-09-15 11:55:02 UTC

Description Ed Santiago 2016-08-08 15:35:45 UTC 
# systemctl start docker-latest
   Job for docker-latest.service failed because the control process exited with error code. [...]

   # systemctl status docker-latest|cat
   ● docker-latest.service - Docker Application Container Engine
      Loaded: loaded (/usr/lib/systemd/system/docker-latest.service; disabled; vendor preset: disabled)
      Active: failed (Result: exit-code) since Mon 2016-08-08 11:18:27 EDT; 31s ago
        Docs: http://docs.docker.com
     Process: 12599 ExecStart=/usr/bin/dockerd-latest daemon --authorization-plugin=rhel-push-plugin --exec-opt native.cgroupdriver=systemd -g /var/lib/docker-latest $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY (code=exited, status=1/FAILURE)
    Main PID: 12599 (code=exited, status=1/FAILURE)

   Aug 08 11:18:27 esm-rhel7-d12-1.localdomain systemd[1]: Starting Docker Application Container Engine...
   Aug 08 11:18:27 esm-rhel7-d12-1.localdomain dockerd-latest[12599]: /usr/bin/dockerd-latest: "/usr/bin/dockerd-latest" requires 0 arguments.
   Aug 08 11:18:27 esm-rhel7-d12-1.localdomain dockerd-latest[12599]: Usage:        dockerd [OPTIONS]
   Aug 08 11:18:27 esm-rhel7-d12-1.localdomain systemd[1]: docker-latest.service: main process exited, code=exited, status=1/FAILURE
   Aug 08 11:18:27 esm-rhel7-d12-1.localdomain systemd[1]: Failed to start Docker Application Container Engine.
   Aug 08 11:18:27 esm-rhel7-d12-1.localdomain systemd[1]: Unit docker-latest.service entered failed state.
   Aug 08 11:18:27 esm-rhel7-d12-1.localdomain systemd[1]: docker-latest.service failed.

This is docker-latest-1.12.0-2.el7.x86_64

Removing the word "daemon" from /usr/lib/systemd/system/docker-latest.service yields:

    # systemctl start docker-latest (fails again)
    # systemctl status docker-latest|cat
    ...
    Aug 08 11:33:24 esm-rhel7-d12-1.localdomain dockerd-latest[12850]: time="2016-08-08T11:33:24.407644145-04:00" level=fatal msg="Failed to connect to containerd. Please make sure containerd is installed in your PATH or you have specificed the correct address. Got error: exec: \"docker-containerd\": executable file not found in $PATH"

docker-containerd is provided by docker-latest but lives in /usr/libexec/docker/docker-containerd
Comment 2 Ed Santiago 2016-08-08 22:54:39 UTC 
docker-latest-1.12.0-3.el7.x86_64 : first problem ("requires 0 arguments") is gone, second problem ("Failed to connect to containerd") persists.
Comment 3 Ed Santiago 2016-08-11 18:21:16 UTC 
Confirmed as fixed in 1.12.0-4.el7
Comment 5 errata-xmlrpc 2016-09-15 08:29:14 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-1829.html
Note You need to log in before you can comment on or make changes to this bug.