Hide Forgot
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.
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".