| Summary: | "executable file not found in $PATH" diagnostic now includes unnecessary/confusing extras | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ed Santiago <santiago> |
| Component: | docker | Assignee: | Antonio Murdaca <amurdaca> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | amurdaca, cevich, dwalsh, lsm5 |
| Target Milestone: | rc | Keywords: | 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: | |
|
Description
Ed Santiago
2016-11-09 21:45:23 UTC
upstream messed this up I guess, tracking upstream at https://github.com/docker/docker/issues/28218 Setting this to medium since it's causing a CI test to fail. I believe this is fixed in the current release. 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".
|