docker inspect [prop ...]

[tj]

similar to #734, but it would help shell scripting primarily (since everything else has nice json parsing readily available usually) to allow something like:

$ sudo docker inspect e5225051a6dc NetworkSettings IPAddress

understandable if it's out of scope, especially with inspect accepting multiple names

[tianon]

I think a new inspect flag (again similar to what's proposed in #734) providing syntax similar to jq's would probably be more flexible and easier for non-Go-writing users to understand than the extremely low-hanging fruit in #734, while also satisfying this one pretty reasonably.

/cc @jpetazzo (because this would be even better than just directly "embedding" jq)

[tj]

IMO even jq does way too much but I guess it depends on the use case. As far as shell scripting goes most of the stuff in jq wouldn't be too useful, and otherwise you have JSON.parse or similar at your disposal in most languages. Personally I think just access to the first container's props via simple dot notation or similar would be ok, but I would see how that might feel incomplete for some people

[jpetazzo]

Don't involve me in UX questions; I suck at that stuff :-)
(But I'm cross-referencing #2921 anyway!)

[crosbymichael]

We implemented docker inspect -format="{{.NetworkSettings.IPAddress }}" ID for generic filtering of properties.