terminology: why "podman container runlabel", not "podman image runlabel"?
more pedantic nitpickery, but i'm a stickler for terminology and i've always defined "image" (or "container image") as, well, something that *can* be run, and "container" as an image in the process of execution. so "podman container runlabel" seems awkward as it clearly(?) refers to an image, not a container. am i overthinking this? rday
On Wed, Nov 6, 2019 at 5:36 PM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
more pedantic nitpickery, but i'm a stickler for terminology and i've always defined "image" (or "container image") as, well, something that *can* be run, and "container" as an image in the process of execution.
so "podman container runlabel" seems awkward as it clearly(?) refers to an image, not a container. am i overthinking this?
All (sub) commands to manage containers are placed under podman-container. Same applies to podman-container-runlabel as it is meant to execute a container (as specified in the image's label). Kind regards, Valentin
On Wed, 6 Nov 2019, Valentin Rothberg wrote:
On Wed, Nov 6, 2019 at 5:36 PM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
more pedantic nitpickery, but i'm a stickler for terminology and i've always defined "image" (or "container image") as, well, something that *can* be run, and "container" as an image in the process of execution.
so "podman container runlabel" seems awkward as it clearly(?) refers to an image, not a container. am i overthinking this?
All (sub) commands to manage containers are placed under podman-container. Same applies to podman-container-runlabel as it is meant to execute a container (as specified in the image's label).
understood, thanks. rday
participants (2)
-
Robert P. J. Day -
Valentin Rothberg