After following instructions the following is printed on the command line:
Successfully built 810c5f1e2c0e
WARNING: Image for service web was built because it did not already exist. To rebuild this image you must use docker-compose build or docker-compose up --build.
http: Hijack is incompatible with use of CloseNotifier in same ServeHTTP call
http: Hijack is incompatible with use of CloseNotifier in same ServeHTTP call
Information
No changes were made to the quick start guide.
No problems found running diagnostics:
Docker for Mac: version: mac-v1.12.0-beta18
OS X: version 10.11.5 (build: 15F34)
logs: /tmp/20160705-231817.tar.gz
[OK] docker-cli
[OK] app
[OK] menubar
[OK] virtualization
[OK] system
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux
Are you sure? https://github.com/docker/compose/issues/3685 says a hotfix was released this morning, but I don’t know where to get it. I’m on (From About) Version 1.12.0-rc3-beta18 (build: 9969) and get the error: [Hi]jack is incompatible with use of CloseNotifier in same ServeHTTP call
$ 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
http: Hijack is incompatible with use of CloseNotifier in same ServeHTTP call
First time I’ve ever seen it. I am also on Version 1.12.0-rc3-beta18 (build: 9969):
$ 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
I just checked for updates in the moby menu and it said I was up to date. This seems to happen when I try to login to more than one container at a time, e.g. I run docker-compose logs for one container and docker-compose exec for another.
Yeah, I"m kind of dead in the water, right now. Can you verify that you’re still seeing the problem I have? All I did was tail the logs in one container and then try to start a login shell in another. Can we mark this thread as not resolved, or should I start another thread?