Given this context:

    # IMG=https://github.com/autotest/autotest-docker/archive/0.7.6.tar.gz
    # docker import $IMG foo

The following command yields inconsistent error messages and exit codes:

    # docker run foo no such command;echo $?

Most of the time, it produces:

    exec: "no": executable file not found in $PATH
    docker: Error response from daemon: Cannot start container <sha>: [9] System error: invalid character ',' looking for beginning of value.
    125        <--- 125 = error in docker daemon itself

Once in a while (~1 in 5) it produces what looks like a sane result:

    exec: "no": executable file not found in $PATH
    docker: Error response from daemon: Container command not found or does not exist..
    127        <--- 127 = command not found (i.e. expected exit status)

And even more rarely (~1 in 8):

    exec: "no": executable file not found in $PATH
    docker: Error response from daemon: Cannot start container <sha>: [9] System error: json: cannot unmarshal string into Go value of type libcontainer.genericError.
    125        <--- docker daemon again

So, yeah, I know: "Docker, Docker, it hurts when I do this." But it would be nice if this produced a consistent 127.

    # rpm -qa|grep docker|sort
    docker-1.9.1-38.el7.x86_64
    docker-common-1.9.1-38.el7.x86_64
    docker-forward-journald-1.9.1-38.el7.x86_64
    docker-latest-1.10.3-19.el7.x86_64
    docker-rhel-push-plugin-1.10.3-19.el7.x86_64
    docker-selinux-1.9.1-38.el7.x86_64
    docker-utils-1.9.1-28.el7.x86_64