graph: add VirtualSize for inspect output

Currently inspect output just shows Size info, and that usally be
very small and even 0 which is confusing.

Fixes #8016

Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
Improve error for docker exec & LXC

Signed-off-by: Victor Vieux <vieux@docker.com>
Fix #6509: Interactive container hangs when redirecting stdout

Cli IsTerminal() SYS_IOCTL operation should be determined from STDIN,
not from STDOUT.

Signed-off-by: Vojtech Vitek (V-Teq) <vvitek@redhat.com>
DockerCli: Check IsTerminal() for both STDIN and STDOUT

`docker events > /tmp/out` should not print control
characters to non-terminal STDOUT.

This addresses commit 26b4a4920adca614f6be17a96f254f331271faf0
without creating regression described in issue #6509.

Signed-off-by: Vojtech Vitek (V-Teq) <vvitek@redhat.com>
Add DockerCli tests

Signed-off-by: Tibor Vass <teabee89@gmail.com>
Adding details on how to use .dockerignore file
Addresses #7724

Signed-off-by: Srini Brahmaroutu <srbrahma@us.ibm.com>
devmapper: include the version in `info`

Signed-off-by: Vincent Batts <vbatts@redhat.com>
Merge pull request #8241 from vbatts/vbatts-devmapper_version

devmapper: include the version in `info`
Update google.md to point to latest container-vm version

In order to match the version listed here:
https://cloud.google.com/compute/docs/containers/container_vms#starting_a_bare_container-vm_instance
API: Provide the HostConfig during "run".

Currently, the HostConfig is only passed from the CLI to Docker only
when issuing a docker create, but not when doing a docker run.

In the near future, in order to allocate ports at creation time rather
than start time, we will need to have the HostConfig readily available
at container creation.

This PR makes the client always pass the HostConfig when creating a
container (regardless of whether it's for a run or create).

Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com>
Merge pull request #8191 from vieux/improve_error_exec_lxc

Improve error for docker exec & LXC
pkg/tarsum: fix panic with dynamic buffer

When read is called on a tarsum with a two different read sizes, specifically the second call larger than the first, the dynamic buffer does not get reallocated causing a slice read error.

Signed-off-by: Derek McGowan <derek@mcgstyle.net> (github: dmcgowan)
Merge pull request #8247 from aluzzardi/f-run-hostconfig

API: Provide the HostConfig during "run".
Merge pull request #8237 from dmcgowan/tarsum_buffer_fix

tarsum: fix panic with dynamic buffer
Merge pull request #8209 from brahmaroutu/doc_dockerignore_7724

Adding details on how to use .dockerignore file
The list of events that 'grep' told me about

docker(master) $ git grep 'LogEvent("' | sed 's/.*("//' | sed 's/").*//'
| sort | uniq | paste -s -d","
create,destroy,die,export,kill,pause,restart,start,stop,unpause

Docker-DCO-1.1-Signed-off-by: SvenDowideit <SvenDowideit@home.org.au> (github: SvenDowideit)
Add the 2 image events found using git grep 'Job("log"'

Docker-DCO-1.1-Signed-off-by: SvenDowideit <SvenDowideit@home.org.au> (github: SvenDowideit)
add wildcard support to copy/add

Signed-off-by: Doug Davis <dug@us.ibm.com>
Gone Camping

Docker-DCO-1.1-Signed-off-by: Sven Dowideit <SvenDowideit@docker.com> (github: SvenDowideit)
Merge pull request #8252 from SvenDowideit/sven-oct-2014-pto

comment out my MAINTAINER line: Gone Camping