baude b1de943eea Better pull error for fully-qualified images ...

When pulling a fully-qualified image that fails, we should not be talking about
registries/search registries in the the error message as it is not applicable.  If
a image that is fq'd and fails to pull, the error should be simplified.

```
$ sudo podman pull this-does-not-exist.example.com/foo
Trying to pull this-does-not-exist.example.com/foo...Failed
error pulling image "this-does-not-exist.example.com/foo": unable to pull this-does-not-exist.example.com/foo: unable to pull image, or you do not have pull access
$
```

Resolves: #1212
Signed-off-by: baude <bbaude@redhat.com>

Closes: #1216
Approved by: mheon

2018-08-06 20:34:29 +00:00

..

testdata

Split refNamesFromImageReference from Runtime.getPullListFromRef

2018-08-01 18:22:58 +00:00

docker_registry_options.go

Remove the forceCompress parameter from getCopyOptions and DRO.GetSystemContext

2018-08-01 18:22:59 +00:00

filters.go

Spell check strings and comments

2018-05-25 08:45:15 +00:00

image_test.go

Skip unit tests which require storage when not running as root

2018-07-26 20:47:31 +00:00

image.go

RFC: Rename runtime.pullImage to runtime.pullImageFromHeuristicSource

2018-08-01 18:22:59 +00:00

parts_test.go

Add unit tests for imageParts

2018-07-23 12:44:38 +00:00

parts.go

Use the result of reference.Parse when checking for digests.

2018-07-23 12:44:38 +00:00

pull_test.go

Replace getPullRefName by Runtime.getPullRefPair

2018-08-02 13:17:17 +00:00

pull.go

Better pull error for fully-qualified images

2018-08-06 20:34:29 +00:00

signing_options.go

Stage3 Image Library

2018-03-14 20:21:31 +00:00

utils.go

Remove the forceCompress parameter from getCopyOptions and DRO.GetSystemContext

2018-08-01 18:22:59 +00:00