Document docker transport is the only supported remote transport#8465
Document docker transport is the only supported remote transport#8465openshift-merge-robot merged 1 commit intocontainers:masterfrom
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
"The image is specified using transport:path format. If no transport is specified, the docker transport will be used by default. For remote Podman, docker is the only allowed transport."
There was a problem hiding this comment.
"Accepts images in archives created by the podman create command."
Also, please explain docker-reference better - I have no idea when and how I should be using it from this description.
There was a problem hiding this comment.
"Accepts a reference to an image in a remote registry. The reference can include a path to a specific registry; if it does not, the registries listed in registries.conf will be queried to find a matching image. By default, credentials from podman login (stored at $XDG_RUNTIME_DIR/containers/auth.json by default) will be used to authenticate; if these cannot be found, we will fall back to using credentials in $HOME/.docker/config.json.
There was a problem hiding this comment.
How do I make a directory like this? Providing a command would greatly help understanding.
There was a problem hiding this comment.
podman push DIR
Would create this or podman pull DIR.
There was a problem hiding this comment.
Podman pull or podman push, podman save.
podman save IMAGE --format docker-dir
There was a problem hiding this comment.
| The `image` uses a "transport":"details" format. | |
| The specified `image` uses a "transport":"details" format. |
There was a problem hiding this comment.
The last two sentences seem to be redundant - the format can be a tag, or a digest, or a digest?
There was a problem hiding this comment.
Everything in this section needs examples - it's extremely unclear how any of this is used in practice.
There was a problem hiding this comment.
Also, we need to make it clear that some of these transports (I think not all?) do not pull the image if it is present locally in c/storage.
There was a problem hiding this comment.
You should probably split what was written for podman run and podman create out into a separate manpage and have all of these reference that page.
pkg/api/handlers/libpod/images.go
Outdated
There was a problem hiding this comment.
If we don't have the Wrapf this can go on the previous line
pkg/api/handlers/libpod/images.go
Outdated
There was a problem hiding this comment.
| An image in a registry implementing the "Docker Registry HTTP API V2". By default, uses the authorization state in `$XDG_RUNTIME_DIR/containers/auth.json`, which is set using `(podman login)`. If the authorization state is not found there, `$HOME/.docker/config.json` is checked, which is set using `(docker login)`. | |
| An image in a registry implementing the "Docker Registry HTTP API V2" format. By default, uses the authorization state in `$XDG_RUNTIME_DIR/containers/auth.json`, which is set using `(podman login)`. If the authorization state is not found there, `$HOME/.docker/config.json` is checked, which is set using `(docker login)`. |
There was a problem hiding this comment.
| An image _docker-reference_ stored in the docker daemon internal storage. _docker-reference_ must contain either a tag or a digest. Alternatively, when reading images, the format can also be docker-daemon:algo:digest (an image ID). | |
| An image in _docker-reference_ format stored in the docker daemon internal storage. _docker-reference_ must contain either a tag or a digest. Alternatively, when reading images, the format can also be docker-daemon:algo:digest (an image ID). |
There was a problem hiding this comment.
| An image _tag_ in a directory compliant with "Open Container Image Layout Specification" at _path_. | |
| An image in a directory compliant with the "Open Container Image Layout Specification" at the specified _path_ and specified with a _tag_. |
Do we have more info io the OCI Layout Spec that we should/can point them to?
docs/source/markdown/podman-run.1.md
Outdated
There was a problem hiding this comment.
Same as prior comments
7cead85 to
1ce978f
Compare
There was a problem hiding this comment.
This is still really unclear about docker-reference - if it's only used when it created, why do we want it here when we're only pulling/using such an image?
|
@mheon @TomSweeneyRedHat PTA Fresh Look. |
There was a problem hiding this comment.
| $XDG_RUNTIME_DIR/containers/auth.json by default) will be used to authenticate; if these cannot be found, we | |
| $XDG_RUNTIME_DIR/containers/auth.json by default) will be used to authenticate; if these cannot be found, |
There was a problem hiding this comment.
| will fall back to using credentials in $HOME/.docker/config.json. | |
| credentials in $HOME/.docker/config.json will be used if available. |
There was a problem hiding this comment.
I'm not sure what to do with "either a tag"? At the very least an "or" is missing or perhaps it's a really bad cut/paste?
There was a problem hiding this comment.
same comments as previous.
The goal is to improve errors when users use the wrong transport in certain cases we stutter, in other cases we don't give enough information. Remove stutters when failing to pull remote images, because of lack of support. Fix errors returned by reference.Parse to wrap in image that was being checked. Fixes: containers#7116 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
|
@mheon @TomSweeneyRedHat PTAL again. Would be nice to get this in to 2.2 release. |
| ## IMAGE | ||
|
|
||
| The image is specified using transport:path format. If no transport is specified, the `docker` (container registry) | ||
| transport will be used by default. For remote Podman, `docker` is the only allowed transport." |
|
One nit then LGTM |
|
Merging as is, I will submit a fix PR later. |
|
/lgtm |
The goal is to improve errors when users use the wrong transport
in certain cases we stutter, in other cases we don't give enough
information.
Remove stutters when failing to pull remote images, because of
lack of support.
Fix errors returned by reference.Parse to wrap in image that was being
checked.
Fixes: #7116
Signed-off-by: Daniel J Walsh dwalsh@redhat.com