Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1393572

Summary: "executable file not found in $PATH" diagnostic now includes unnecessary/confusing extras
Product: Red Hat Enterprise Linux 7 Reporter: Ed Santiago <santiago>
Component: dockerAssignee: Antonio Murdaca <amurdaca>
Status: CLOSED CURRENTRELEASE QA Contact: atomic-bugs <atomic-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: amurdaca, cevich, dwalsh, lsm5
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-30 14:56:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ed Santiago 2016-11-09 21:45:23 UTC 
At some point along the docker-1.12 process, the error message for "command not found" changed:

   # docker run centos no-such-binary

   - Error response from daemon: oci runtime error: exec: "no-such-binary": executable file not found in $PATH.

   + Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"exec: \\\"no-such-binary\\\": executable file not found in $PATH\"\n".

That is: there is now a spurious "invalid header field value etc etc". And the escaped quotes.

Present in docker-1.12.3-1.el7 , docker-1.12.3-4.el7 , docker-latest-1.12.3-2.el7 (and probably many more) but, curiously, not in docker-latest-1.12.1-3.el7.
Comment 1 Antonio Murdaca 2016-11-09 23:20:22 UTC 
upstream messed this up I guess, tracking upstream at https://github.com/docker/docker/issues/28218
Comment 3 Chris Evich 2017-02-21 14:36:53 UTC 
Setting this to medium since it's causing a CI test to fail.
Comment 4 Daniel Walsh 2017-06-30 14:56:45 UTC 
I believe this is fixed in the current release.
Comment 5 Ed Santiago 2017-07-03 13:53:41 UTC 
Seems to be fixed in 1.13:

   docker-latest-1.13.1-19.1.git19ea2d3.el7:
    /usr/bin/docker-latest: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: \"no-such-binary\": executable file not found in $PATH".

FWIW, not in 1.12:

  docker-1.12.6-39.1.git6ffd653.el7:
    /usr/bin/docker-current: Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"exec: \\\"no-such-binary\\\": executable file not found in $PATH\"\n".