New docker client is not working with VIC [v1.13]

[caglar10ur]

New docker client is not working with VIC [version 1.13] and that needs to be documented somewhere.

• determine source of hang (but not fix)
• document as known issue for current VIC release.

The original issue is tracked at #3720

[mdubya66]

works for me

[mdubya66]

Closing this. Added kind/note to the original issue #3720

[hickeng]

I'd like to determine what the problem is so we can document it appropriately as a high priority in the near term.

This is separated from the original issue as the two hypothesis raised both imply potentially long and involved fixes:
a. client is now using event stream (unsupported) to determine container exit
b. parameters have been switched in the API update (tied to outcome of #3415)

[caglar10ur]

This is what I'm observing but this is a build from my branch. Will try switching back to master

[vagrant@devbox:/opt/go/src/github.com/vmware/vic(3605)] docker version
Client:
 Version:      1.13.0
 API version:  1.23
 Go version:   go1.7.3
 Git commit:   49bf474
 Built:        Tue Jan 17 09:58:26 2017
 OS/Arch:      linux/amd64

Server:
 Version:      0.8.0
 API version:  1.23 (minimum version )
 Go version:   go1.7.4
 Git commit:   dcff4f6
 Built:        Thu Jan 26 18:43:51 2017
 OS/Arch:      linux/amd64
 Experimental: true
[vagrant@devbox:/opt/go/src/github.com/vmware/vic(3605)] docker ^Cllo-world
[vagrant@devbox:/opt/go/src/github.com/vmware/vic(3605)] docker run ubuntu uname
Unable to find image 'ubuntu:latest' locally
Pulling from library/ubuntu
8aec416115fd: Pull complete
695f074e24e3: Pull complete
946d6c48c2a7: Pull complete
bc7277e579f0: Pull complete
2508cbcde94b: Pull complete
a3ed95caeb02: Pull complete
Digest: sha256:0c01b5105fc57b5eb8b7bb1d697b9dc5602022f69a0a33bf282b117e7a754a91
Status: Downloaded newer image for library/ubuntu:latest

Linux



^C^C^C

[caglar10ur]

Same problem with master so not sure what are you doing differently @mdubya66. Can you try running "docker run ubuntu uname"?

[mdubya66]

This hangs on mac as well. Control-C does nothing. kill -9 was required. The container still reports as being running after the kill.

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2cd453dede6e ubuntu "uname" 5 days ago Up About a minute backstabbing_liskov

[stuclem]

Apologies for getting to this so late (have had a huge backlog that I have only just cleared). Proposed text for the release notes:

• vSphere Integrated Containers Engine 0.8 does not support Docker Client 1.13. #3734, #3734
  If you attempt to connect version 1.13 of the Docker Client to a virtual container host, the Docker client stops working.
  Workaround: Use version 1.12 of the Docker Client to connect to virtual container hosts.

@sflxn, @caglar10ur, @mdubya66 does this cover it?

[sflxn]

@stuclem this is only a temporary situation. It will get fixed. Do you want to take this issue for documentation? I'll take #3720.

[sflxn]

I'm going to comment in the original issue for all technical discussions from here on out.

[stuclem]

No problem, @sflxn. Here's an updated version of the release note entry for 0.8, that I have added in https://github.com/vmware/vic/releases/tag/v0.8.0:

• vSphere Integrated Containers Engine 0.8 does not support Docker Client 1.13. #3734, #3734
  If you attempt to connect version 1.13 of the Docker Client to a virtual container host, the Docker client stops working. This happens because Docker 1.13 uses Docker Events, which vSphere Integrated Containers Engine 0.8 does not support.
  Workaround: Use version 1.12 of the Docker Client to connect to virtual container hosts.

Is this OK? Thanks!

[stuclem]

Incidentally, @caglar10ur @mdubya66 @mhagen-vmware, the main docs for 0.8 currently state support for Docker 1.11.2. Should we update this to state "versions up to 1.12, but not 1.13"?

[sflxn]

@stuclem I would say "which vSphere Integrated Containers Engine 0.8 does not yet support." We're going to get docker events implemented. It's not just for docker 1.13 run but also for docker stats.

[stuclem]

Done. Thanks @sflxn. Since this issue is just for doc, closing.