Doug Davis ac043c7db6 Fix docker import tests ...

For me when I run the test I see:
```
Downloading from http://nourl/bad
Importing    283 B
Untar re-exec error: exit status 1: output: unexpected EOF
```
and nothing about "dial tcp" so it appears that the output is
system dependent and therefore we can't really check it. I think
checking for non-zero exit code is sufficient so I'm removing this
string check.

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

2016-05-23 15:34:40 -07:00

..

archive_test.go

Windows CI: Unit Tests stop running failing chrootarchive tests

2016-03-01 14:28:29 -08:00

archive_unix.go

Fix docker import tests

2016-05-23 15:34:40 -07:00

archive_windows.go

…

archive.go

Correct build-time directory creation with user namespaced daemon

2015-10-20 08:59:48 -04:00

chroot_linux.go

pkg: chrootarchive: chroot_linux: fix docker build

2016-05-10 00:42:49 +02:00

chroot_unix.go

Use pivot_root instead of chroot for chrootarchive

2016-05-04 19:55:34 -04:00

diff_unix.go

Remove flush(stdout) in pkg/chrootarchive/diff_unix.go and improve error reporting of flush() to fix #21103

2016-03-15 10:29:51 -07:00

diff_windows.go

…

diff.go

…

init_unix.go

Remove flush(stdout) in pkg/chrootarchive/diff_unix.go and improve error reporting of flush() to fix #21103

2016-03-15 10:29:51 -07:00

init_windows.go

…