Docker Community Forums

Share and learn in the Docker community.

[RESOLVED] Error: "http: Hijack is incompatible with use of CloseNotifier in same ServeHTTP call" with docker-compose


(Jkilbride) #1

Expected behavior

Being able to interact with multiple containers simultaneously using docker-compose.

Actual behavior

Interacting with more than one container produces the subject error.

Information

Diagnostic ID: A72A1695-9156-46A5-A920-2A3869BA1AE4

Docker for Mac: version: mac-v1.12.0-beta18
OS X: version 10.11.5 (build: 15F34)
logs: /tmp/20160706-110639.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

Docker Version:

$ 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

Steps to reproduce the behavior

  1. Use the following docker-compose.yml:

    version: “2”

    services:
    redis:
    image: redis:3.0-alpine
    container_name: redis
    networks:
    - private

    nginx:
    image: nginx:1.9-alpine
    container_name: nginx
    ports:
    - "8080:80"
    networks:
    - private

    networks:
    private:
    driver: bridge

  2. Run docker-compose up -d

  3. Tail the redis container logs:
    docker-compose logs -f redis

  4. In a separate terminal window, attempt to login to the nginx container:
    docker-compose exec nginx sh -l

This produces the following:

$ docker-compose exec nginx sh -l
http: Hijack is incompatible with use of CloseNotifier in same ServeHTTP call

This only started occurring with the latest update. It is the first time I have ever encounter this type of error.


(Misky1986) #2

I have experienced the excact same. Need to go back to toolbox while this error is fixed.


(Jkilbride) #3

UPDATE:

This error is actually occurring anytime I try to login to a container. There’s no need to tail the logs of another container first, as mentioned in my initial post. So, it’s actually worse than I originally thought…

I may have to revert to toolbox until this is fixed, also.


(Jkilbride) #4

This error has been resolved with the latest update this morning:

Version 1.12.0-rc3-beta18 (build: 9996)

Thanks!