moby: "Unrecognized input header" interrupting docker client

I am seeing this in 1.10.0 rc1 and rc2 about 5~10% of the time.

The docker run client exited with “Unrecognized input header” after a few minutes, but the container was still running and you can see new output with docker logs -f

The docker run cmmand is: (simplified just to show what switches are being used)

docker run --entrypoint /sbin/smell-baron --name somename -h somehost --volumes-from somevolume -e BRANCH=foo -v /path/to/devscript:/devscript $IMAGE bash -l /devscript/build.sh

I don’t have a small reproducible case at the moment though.

docker inspect the container shows: (looks very normal)

        "State": {
            "Status": "exited",
            "Running": false,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 0,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2016-02-02T21:10:56.5227335Z",
            "FinishedAt": "2016-02-02T21:15:22.471208248Z"
        },

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 1
  • Comments: 58 (26 by maintainers)

Commits related to this issue

Most upvoted comments

That makes sense, if -t is used then ultimately stdcopy is not used.