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>
bump Go to 1.3.2

Docker-DCO-1.1-Signed-off-by: Cristian Staretu <cristian.staretu@gmail.com> (github: unclejack)
Fix #7843

When doing `docker start -a` on a container that won't start, terminal
was getting stuck on the attach, even after container removal.

Docker-DCO-1.1-Signed-off-by: Brian Goff <cpuguy83@gmail.com> (github: cpuguy83)
Merge pull request #8224 from cpuguy83/7843_fix_start_attach_error_hang

Fix #7843 start -a can cause frozen term
Merge pull request #8254 from unclejack/bump_go_to_1.3.2

bump Go to 1.3.2
Merge pull request #8233 from tiborvass/pr-7658

Fix Interactive container hangs when redirecting stdout
Fix #8259 - Can't reuse symlink'd bindmount

volumes.Get was not checking for symlinked paths meanwhile when adding a
new volume it was following the symlink.
So when trying to use a bind-mount that is a symlink, the volume is
added with the correct path, but when another container tries to use the
same volume it got a "Volume exists" error because volumes.Get returned
nil and as such attempted to create a new volume.

Docker-DCO-1.1-Signed-off-by: Brian Goff <cpuguy83@gmail.com> (github: cpuguy83)
Merge pull request #8260 from cpuguy83/8259_fix_bindmount_symlink_reuse

Fix #8259 - Can't reuse symlink'd bindmount