When I run pack inspect-image <image>Then I see the following information in the output
Processes:
TYPE SHELL COMMAND ARGs
web (default) bash /path/to/executable some args
worker /another/command some arg
Thenpack prints a tip
Tip: To run a particular process or an arbitrary command
'docker run <image> <process-type>', or
'docker run <image> <cmd>'
Backwards compatibility (no processes array in label)
Given an image, <image> with a io.buildpacks.build.metadtata label, that is missing the proccesses key
When I run pack inspect-image <image>Then I see no Processes: block in the output, or tip
No processes (empty processes array in label)
Given an image, <image> with a io.buildpacks.build.metadtata label, with the following metadata in the io.buildpacks.build.metadtata label
{"processes": []}
When I run pack inspect-image <image>Then I see the following Processes: block
Processes:
(none)
Thenpack will print a warning instead of a tip
Warning: image has no process types, a command must be supplied at runtime:
'docker run <image> <cmd>'
Depends on buildpack/lifecycle#206
Happy Path
Given an image,
<image>
with the following metadata in theio.buildpacks.build.metadtata
labelWhen I run
pack inspect-image <image>
Then I see the following information in the outputThen
pack
prints a tipBackwards compatibility (no
processes
array in label)Given an image,
<image>
with aio.buildpacks.build.metadtata
label, that is missing theproccesses
key When I runpack inspect-image <image>
Then I see noProcesses:
block in the output, or tipNo processes (empty
processes
array in label)Given an image,
<image>
with aio.buildpacks.build.metadtata
label, with the following metadata in theio.buildpacks.build.metadtata
labelWhen I run
pack inspect-image <image>
Then I see the followingProcesses:
blockThen
pack
will print a warning instead of a tip