Replies: 1 comment
-
I forgot to mention the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm trying to figure out (
podman
) concepts ofrepository
,name
andtag
which does not seem to be as trivial as it may seem:I took a look at different documents, including image and distribution OCI specs and this
Redhat
document.My first understanding was that basically naming could be broken down like this:
registry/namespace/subnamespace/img_name:tag
which is I think what anyone does when actually using images and running containers.
For a
podman image list
output looks like this:I'd tend to consider that image name is
rhel88
, tag is1
and namespace is eitherlocalhost/prod
(or justprod
?)But I'm not so sure as I also notice the following facts:
podman
Python
API the repository concept does not seem to be listable, although it is required for theimage.tag()
methodrepository
viapodman command line
seems to be listed astags
via thePython API
(through theimage.tags
member), so this would differ from the concept oftag
as the suffix after the:
and listed in theTAG
column ofimage list
commandtag
as a human readable reference to image manifest, so API would seem to be correct for that matter ?Can you help me clarify what's what in which context
A simple example would be : suppose you want, with the API to move the
latest
tag to a particular image version : you'd have to extract the repository first from your target image full name (let's saylocalhost/prod/rhel88:2
) in order to make it the first parameter of thetag()
method. But this repository name, if I'm correct, would only be computable through thetag
member but which a) may llist multiple items and b) include the:xxx
"tag"Thanks for your help
--
Thomas HUMMEL
Beta Was this translation helpful? Give feedback.
All reactions