ContainerList leaves .Mounts empty about engine-api HOT 4 CLOSED

@msterin I think it's expected with the 1.10 daemon. The Mount attribute in the types.Container is populated by the daemon in 1.11 (we added Mounts to ps and the possibility to filter using it).

Using a daemon 1.11.0-rc2 :

$ go run est.go 
2016/04/02 10:59:32 Connected to unix:///var/run/docker.sock
2016/04/02 10:59:35 9 containers found
2016/04/02 10:59:35 total refcount: using List 1 using Inspect 1

from engine-api.

@vdemeester - thanks ! It does look sloppy to leave a field selectively filled in by some APIs with zero comments and zero doc, but since it's not my misunderstanding of the API but a bug in 1.10 (fixed in 1.11 per your run) I will just stick with ContainerInspect then.

from engine-api.

It's more about version than a bug, you talking to a 1.10 daemon with a v1.11 api lin'. It's retro compatib!e so it works, but some field don't get filed 😇

from engine-api.

It's more about version than a bug, you talking to a 1.10 daemon with a v1.11 api lin'. It's retro compatib!e so it works, but some field don't get filed

Nice wordsmithing :-) ! On my books, it is still a bug - I am talking to 1.10 with 1.10 API (see below) but it's beyond the point - your post cleared up what's going on so it's all good. Thanks again.

Per https://docs.docker.com/engine/reference/api/docker_remote_api/

Docker version  API version     Changes
1.10.x              1.22         API changes

So I thought I was talking to 1.10 daemon with 1.10 API. .Mounts field was added to engine-API in early February and I picked the code in March. I did not see anything in the 1.22 APi definition which indicates that one API fills the filed in, and another does not.

from engine-api.