From 58f840462c344d284f2511dd0eafb386560d6e8f Mon Sep 17 00:00:00 2001 From: Tomas Volf Date: Tue, 23 Aug 2022 13:54:07 +0200 Subject: [PATCH] Document limitations of transports for remote podman client When using remote podman client, not all transports work as expected. So document this limitation. Fixes: containers/podman#15141 Signed-off-by: Tomas Volf --- docs/containers-transports.5.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/containers-transports.5.md b/docs/containers-transports.5.md index 6c94d0a1..b79f1e59 100644 --- a/docs/containers-transports.5.md +++ b/docs/containers-transports.5.md @@ -11,6 +11,11 @@ containers-transports - description of supported transports for copying and stor Tools which use the containers/image library, including skopeo(1), buildah(1), podman(1), all share a common syntax for referring to container images in various locations. The general form of the syntax is _transport:details_, where details are dependent on the specified transport, which are documented below. +The semantics of the image names ultimately depend on the environment where +they are evaluated. For example: if evaluated on a remote server, image names +might refer to paths on that server; relative paths are relative to the current +directory of the image consumer. + ### **containers-storage**:[**[**storage-specifier**]**]{image-id|docker-reference[@image-id]} An image located in a local containers storage.