Compose: "http: Hijack is incompatible with use of CloseNotifier in same ServeHTTP call" errors

[justincormack]

Using 1.8-rc1 and docker 1.12-rc3 with the following compose file:

version: '2'
services:
  test:
    build:
      context: .

and Dockerfile:

FROM alpine

If I do:

whale:comprun justin$ docker-compose build test
Building test
Step 1 : FROM alpine
 ---> f70c828098f5
Successfully built f70c828098f5
whale:comprun justin$ docker-compose run test ls
http: Hijack is incompatible with use of CloseNotifier in same ServeHTTP call
                                                                             http: Hijack is incompatible with use of CloseNotifier in same ServeHTTP call
                                                                                                                                                          whale:comprun justin$ 

Looks like a missed case in https://github.com/docker/compose/pull/1374

cc @dnephin

[SantoDE]

I now have the same issue. Just upgraded and my compose setup refuses to start :(

[jonniedarko]

@SantoDE I was able to restart after I removed all containers , I still get the log jack is incompatible with use of CloseNotifier in same ServeHTTP call and no other log outs (which is concerning) but everything seems to be running fine

[SantoDE]

@jonniedarko oh you are right. The containers are up, but I dont have any more logs. Still an issue then I guess :/ cc: @justincormack

[DejaAugustine]

Docker version 1.12.0-rc3, build 91e29e8, experimental is pretty much non-functional for me due to this bug.

I was lucky in that I still had an old Docker.dmg from May with Docker version 1.11.0, build 4dc5990 on it, but this change is seriously breaking.

[PatrickDRusk]

Busted in Boston, too.

[SantoDE]

Hopefully the docker team can fix that fast :/

[javawolfpack]

Fingers crossed... was having no issues until I just installed the update. Had this one after fixing another that required me to rebuild my containers...

[JonathanTech]

Well, I get that error, but if I run docker-compose in daemon mode everything seems to be working fine.

[JonathanTech]

I can still attach using docker exec -it bash and everything is working as expected. docker attach also works as expected.

[javawolfpack]

I need to run one of my containers in bash currently... so this is causing a significant headache :(

[dnephin]

Did this just start happening with RC3? It was fine with RC2?

[emgeee]

+1 for this issue. Just upgraded to Docker for Mac Version 1.12.0-rc3-beta18 (build: 9969) and I'm running into this issue

[javawolfpack]

@JonathanTech that's interesting... maybe I can run it manually but fails when I try interactive bash from compose.

[SantoDE]

@dnephin Yep, RC2 was fine. Just right after I upgraded to RC3 the madness started.

[milehimikey]

+1 on this issue as of RC3

[javawolfpack]

+1 only happened when I upgraded to Version 1.12.0-rc3-beta18 (build: 9969) minutes ago

[antipin]

+1 for Version 1.12.0-rc3-beta18 (build: 9969)

[antipin]

Anybody knows how to downgrade to RC2?

[praveenperera]

+1 for Version 1.12.0-rc3-beta18 (build: 9969)

[PatrickDRusk]

@antipin, I can't find a back-rev to download.

I am able to docker exec into a container that is apparently hung when I do the docker-compose run.

[jzimmek]

+1 for Version 1.12.0-rc3-beta18 (build: 9969)

[eko]

I also have this issue with same version (1.12.0-rc3-beta18 (build: 9969)) just after the upgrade.

[imnotquitejack]

+1 for Version 1.12.0-rc3-beta18 (build: 9969)

[erinnichols]

+1, Version 1.12.0-rc3-beta18 (build: 9969)

[JonathanTech]

FYI - for the devs - Diagnostic ID : 705F4449-0DA5-43A4-9BC3-2AD6F1FF15F3

[praveenperera]

Found the old build in the Trash (9779) works again

[javawolfpack]

I have the docker.dmg on another computer for Version 1.12.0-rc2-beta17 (build: 9779), hoping I can install it over the new one.

[mathportillo]

+1, Version 1.12.0-rc3-beta18 (build: 9969)

[visokoo]

Running into the same problem after updating, now reverting back to rc2 for the time being...

[javawolfpack]

So old installer allowed me to roll back and now working... I'd share the dmg, but not really good to trust links from strangers on the net.

[antipin]

Yay! pevious version in fact can be found in trash (on OSX)

[mckn]

+1

[gvc]

Thank god for the Thrash

[EugenMayer]

How can such a thing slip through QA, beta, alpha or whatever.

Coming from docker, you kind expected to see a CI, right.

[ograycode]

Can confirm that this happens on python:2.7 and node:6.2 containers when running docker compose commands. Reverted back to 9779 and told my team not to upgrade because the next build is broken.

[PatrickDRusk]

And I will never empty my trash again...

[aethant]

Happened to me with node:6.1 and mongo:latest. Reverted to 9779 and rebuilt containers, working for now.

[skwp]

same problem, 1.12-rc3 sinatra app

[FrenchBen]

@EugenMayer https://github.com/docker/docker/issues/24343#issuecomment-230599107

[iwaffles]

Seeing the same issue here with 1.12-rc3 using the redis container image: redis:2.8.23

[iwaffles]

For what it's worth, downloading the old version and replacing it with the new version worked flawlessly for me on Mac: https://github.com/docker/docker/issues/24343#issuecomment-230605770

[Chekote]

Roll back to Beta17 until this is fixed: https://download.docker.com/mac/beta/1.12.0.9779/Docker.dmg

[sonnyvan]

Thanks everyone for the rollback idea. I found beta 17 in my Trash and docker-compose run works again.

[justincormack]

Apologies for this. This does not appear to be a compose bug, it is a Docker for Mac specific issue, and we will be rolling out a fix as soon as possible. In the mean time please see the download links for old versions https://github.com/docker/docker/issues/24343#issuecomment-230599107 if you updated.

[vkrol]

I see this message on Windows too.

[justincormack]

Apologies for this, a hotfix has been released and it should be safe to update.

[Manoj-nathwani]

Updated to latest version of docker which fixed the issue 😄

[jonniedarko]

+1

On Wed, Jul 6, 2016, 8:13 AM Manoj Nathwani [email protected]
wrote:

Updated to latest version of docker which fixed the issue 😄

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/compose/issues/3685#issuecomment-230754261,
or mute the thread
https://github.com/notifications/unsubscribe/ADgPVy99v0JjGB6Kkm9Hu_mjY8FhugmGks5qS5vygaJpZM4JEgw5
.

[cap10morgan]

Running the latest Docker for Mac that mine says is available (1.12.0-rc3-beta18 build: 9969), I still get this error trying to bring up docker-compose stacks.

[jamshid]

@justincormack where is the hotfix? "Check for updates" says my rc3 Beta 18 is the latest but I still get the [Hi]jack is incompatible with use of CloseNotifier in same ServeHTTP call error.

$ docker version
Client:
 Version:      1.12.0-rc3
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   91e29e8
 Built:        Sat Jul  2 00:09:24 2016
 OS/Arch:      darwin/amd64
 Experimental: true

Server:
 Version:      1.12.0-rc3
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   876f3a7
 Built:        Tue Jul  5 02:20:13 2016
 OS/Arch:      linux/amd64
 Experimental: true

[gitnickgit]

current master should be rolled back and set as current release. This way new users don't get something that is broken right off the bat.

[antipin]

Docker version 1.12.0-rc3, build 91e29e8, experimental
Still have this error:

Creating api_data_1
Creating api_db_1
Creating api_api_1
Attaching to api_data_1, api_db_1, api_api_1
db_1    | jack is incompatible with use of CloseNotifier in same ServeHTTP call
api_1   | jack is incompatible with use of CloseNotifier in same ServeHTTP call
data_1  | jack is incompatible with use of CloseNotifier in same ServeHTTP call
api_data_1 exited with code 0

[antipin]

Uninstall docker and download beta-17 from site seems to be a solution: https://download.docker.com/mac/beta/Docker.dmg

[simonamdev]

I just started getting this issue this morning and I'm on windows. I did check for updates at it says I am up to date.

docker version

[justincormack]

Sorry, we pulled the update temporarily for other reasons. If you still have the issue, you can reinstall the previous version or wait a few hours.

[tejasmanohar]

@antipin I'm getting beta-18 when I use that link. know if there's an archive somewhere?

[antipin]

@tejasmanohar if you for some reason can't recreate your containers, the only solution I saw is here https://github.com/docker/docker/issues/24343#issuecomment-230887236

If you are using docker in a right way and don't persist your data inside containers, I guess you have no reason not to update to the latest version, recreate containers and it will be ok ;)

[FrenchBen]

@tejasmanohar @antipin we also documented it here:
https://docs.docker.com/docker-for-mac/troubleshoot/#/recreate-or-update-your-containers-after-beta-18-upgrade