Image [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Image ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]

===== Discussion =====

An Image is an identifiable [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] that packages software, configuration, files, metadata, and other content used to instantiate a computing subject.

An Image may be used to instantiate:

  * A virtual machine
  * A containerized workload
  * A computing device
  * A platform component
  * A runtime environment
  * Another deployable computing subject

An Image may contain:

  * Executable software
  * Operating-system content
  * Runtime libraries
  * Application files
  * Configuration files
  * Startup instructions
  * Security controls
  * Dependency information
  * Identifying metadata
  * One or more [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layers]]

An Image may participate in:

  * Image building
  * Image composition
  * Image signing
  * Image verification
  * Compliance assessment
  * Image promotion
  * Repository publication
  * [[dido:99_annexes:annex-b-terms-and-definitions:o:offline_transfer|Offline Transfer]]
  * Deployment
  * Replacement
  * [[dido:99_annexes:annex-b-terms-and-definitions:r:retirement|Retirement]]

An Image differs from an instance:

  * An Image is the Artifact used to instantiate a computing subject
  * An instance is a realized computing subject created from an Image

Multiple instances may originate from the same Image while maintaining separate runtime state.

An Image differs from an [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layer]]:

  * An Image is the complete Artifact used to instantiate a computing subject
  * An Image Layer is an identifiable unit of content incorporated into an Image

Specializations of Image include:

  * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:container_image|Container Image]]

===== Definition =====

//identifiable artifact that packages software, configuration, files, metadata, and other content used to instantiate a computing subject//

===== Source =====

Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

===== Note =====

In Crucible documentation, **Image** refers to a deployable computing Artifact rather than a photograph, diagram, graphical representation, or filesystem backup unless the surrounding text explicitly establishes another meaning.

An Image may be identified by:

  * A name
  * A tag
  * A content digest
  * A [[dido:99_annexes:annex-b-terms-and-definitions:r:revision|Revision]] identifier
  * A release identifier
  * A combination of identifiers

An Image does not by itself establish that the Image is:

  * Approved
  * Signed
  * Verified
  * Free from vulnerabilities
  * Compliant with an applicable [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]
  * Authorized for deployment
  * Compatible with a target platform
  * Suitable for a specified purpose

Separate requirements govern those determinations.

The term does not prescribe a particular image format, build tool, repository, runtime, virtualization platform, container platform, operating system, or [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementation]].

===== Example =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] builds an Image containing controlled software, configuration, runtime files, security controls, and identifying metadata. A deployment process later uses the Image to instantiate a virtual machine or containerized workload.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>