public:99_annexes:annex-b-terms-and-definitions:b:base_image

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:b:base_image [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:b:base_image [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Base Image ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Base Image is a [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] that provides the common operating system, storage, services, configuration, and security foundation for one or more derived images.
 +
 +The Base Image may contain an installed operating system, disk partitions, filesystems, core packages, system services, user and access settings, network configuration, security controls, and other shared capabilities.
 +
 +A Base Image reduces duplication by allowing later image builds to add specialized packages, services, configurations, or capabilities without repeating the complete operating-system installation.
 +
 +Within Crucible, a Base Image may serve as the source for a hardened guest image or a later [[public:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layer]].
 +
 +===== Definition =====
 +
 +//[[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|machine image]] that provides the common operating-system, storage, service, configuration, and security foundation for one or more derived images//
 +
 +===== Source =====
 +
 +Generalized from virtualization, cloud computing, operating-system deployment, container-image, and machine-image engineering usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +A Base Image does not necessarily satisfy every security, compliance, or workload requirement of a deployed system.
 +
 +The term identifies the image’s role as a reusable foundation rather than a particular level of hardening, approval, or completeness.
 +
 +===== Example =====
 +
 +Crucible builds a [[public:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 Base Image containing the installed operating system, configured filesystems, essential packages, and shared system services. Later image layers add security hardening and Kubernetes capabilities.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>