Skip to content

Conversation

aanand
Copy link

@aanand aanand commented Apr 29, 2015

This ensures that the connection is not recycled, which can cause the Docker daemon to complain if we perform two streaming actions in a row.

Closes #1275.

@LK4D4
Copy link

LK4D4 commented Apr 29, 2015

@aanand Not sure what's going on, but you need to close it after each build :) Sorry if this is exactly what you done.

@aanand aanand force-pushed the close-before-attaching branch from 93debf5 to a5c1445 Compare April 29, 2015 17:32
@aanand aanand changed the title Close connection before attaching on 'up' and 'run' Close connection after building or pulling Apr 29, 2015
@aanand
Copy link
Author

aanand commented Apr 29, 2015

@LK4D4 Ah, good point. I've made it close after every build or pull.

@LK4D4
Copy link

LK4D4 commented Apr 29, 2015

@aanand Why pull? :) CloseNotifier used only in POST /build.

This ensures that the connection is not recycled, which can cause the
Docker daemon to complain if we've already performed another streaming
call such as doing a build.

Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
@aanand aanand force-pushed the close-before-attaching branch from a5c1445 to 1a77fee Compare April 29, 2015 17:42
@aanand
Copy link
Author

aanand commented Apr 29, 2015

Oh, I assumed it applied to anything with streaming. Just build then.

@dnephin
Copy link

dnephin commented Apr 29, 2015

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

APIError: 500 Server Error on first docker-compose up / build
4 participants