mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
20 lines
1.7 KiB
Plaintext
20 lines
1.7 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// microshift_install_bootc/microshift-about-rhel-image-mode
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="microshift-bootc-conc_{context}"]
|
|
= About image mode for {op-system-base-full}
|
|
|
|
By using image mode for {op-system-base}, you can use the same tools and techniques for the operating system that you use with application containers. Image mode for {op-system-base} is a deployment method that uses a container-native approach to build, deploy, and manage the operating system as a `rhel-bootc` image.
|
|
|
|
* This container image uses standard OCI or Docker containers as a transport and delivery format for base operating system updates.
|
|
* A bootc image includes a Linux kernel that is used to start the operating system.
|
|
* By using bootc containers, developers, operations administrators, and solution providers can all use the same container-native tools and techniques.
|
|
|
|
Image mode for {op-system-base} splits the creation and installation of software changes into two steps: one on a build system and one on a running target system.
|
|
|
|
* In the build-system step, a Podman build inspects the RPM files available for installation, determines any dependencies, and creates an ordered list of chained steps to complete. Along with any other system configuration steps taking place, the end result is a new operating system available to install.
|
|
|
|
* In the running-target-system step, a bootc update downloads, unpacks, and prepares the new operating system to be started alongside the currently running system. Local configuration changes are carried forward to the new operating system. These changes take effect only when the system is restarted and the new operating system image replaces the previously running one.
|