Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v1.13] docker client hangs #3720

Closed
caglar10ur opened this issue Jan 25, 2017 · 9 comments
Closed

[v1.13] docker client hangs #3720

caglar10ur opened this issue Jan 25, 2017 · 9 comments
Assignees
Labels
area/cli The Vritual Container Host management CLI (vic-machine) area/docker Support for the Docker operations priority/p0
Milestone

Comments

@caglar10ur
Copy link
Contributor

caglar10ur commented Jan 25, 2017

running docker run hello-world using 1.13 client ends up with a hung client. The underlying VM starts and then powers off as expected. Tether, portlayer and personality logs shows no errors. Looking at the pporf output suggests that the client waits an event. Using v1.12 client works as expected.

@caglar10ur caglar10ur added area/cli The Vritual Container Host management CLI (vic-machine) area/docker Support for the Docker operations kind/bug/p0 priority/p0 labels Jan 25, 2017
@caglar10ur
Copy link
Contributor Author

logs.zip

@caglar10ur
Copy link
Contributor Author

This could be related with the API version piece as client seems to waiting docker events to arrive. Raising another one for documenting the fact that we don't support new client versions.

@mdubya66 mdubya66 added the impact/doc/note Requires creation of or changes to an official release note label Jan 26, 2017
@mdubya66
Copy link
Contributor

did hello world ever work? iirc we had problems all along with the default one.

@caglar10ur
Copy link
Contributor Author

Yes, hello-world works fine with older clients

@mhagen-vmware mhagen-vmware added this to the Sprint 2 milestone Feb 1, 2017
@sflxn sflxn self-assigned this Feb 1, 2017
@stuclem
Copy link
Contributor

stuclem commented Feb 8, 2017

Added proposed release note entry in #3734.

@sflxn
Copy link
Contributor

sflxn commented Feb 8, 2017

I've identified the new code that is causing the hang. The 1.13 CLI changed the run code to now subscribe to events, which we have not yet implemented. It's waiting on an event from the daemon that says the container died, detached, or was destroyed. It appears they have switched to using events instead of container wait to determine if the container has exited.

The only way to fix this is to implement events subscription.

@stuclem
Copy link
Contributor

stuclem commented Feb 9, 2017

Removing kind/note from this one as the RN update is being tracked in #3734.

@stuclem stuclem removed the impact/doc/note Requires creation of or changes to an official release note label Feb 9, 2017
@sflxn
Copy link
Contributor

sflxn commented Feb 10, 2017

Deliverable for this issue:

#2252 for event subscription manager on portlayer side
#367 for event subscription on personality side

Acceptance criteria for events will be new docker command robot scripts for events. Specifically, for docker run, we need to check for "die", "detach", and "destroy".

@mhagen-vmware
Copy link
Contributor

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cli The Vritual Container Host management CLI (vic-machine) area/docker Support for the Docker operations priority/p0
Projects
None yet
Development

No branches or pull requests

6 participants