diff options
| author | baude <bbaude@redhat.com> | 2018-08-04 10:30:16 -0500 |
|---|---|---|
| committer | Atomic Bot <atomic-devel@projectatomic.io> | 2018-08-06 20:34:29 +0000 |
| commit | b1de943eea26bf1f6a6c599116cba3e7d9fe5d36 (patch) | |
| tree | 966daeb210fbd19cd51571d26bbbf6f595f545d3 /docs/podman-exec.1.md | |
| parent | e90909735cb926278a7faa1081cecdf767676f87 (diff) | |
| download | podman-b1de943eea26bf1f6a6c599116cba3e7d9fe5d36.tar.gz podman-b1de943eea26bf1f6a6c599116cba3e7d9fe5d36.tar.bz2 podman-b1de943eea26bf1f6a6c599116cba3e7d9fe5d36.zip | |
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
Diffstat (limited to 'docs/podman-exec.1.md')
0 files changed, 0 insertions, 0 deletions