You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: fix versions, provider lists, and broken internal links (#439)
* docs: align documentation with latest code
* docs: fix broken internal links and complete provider lists
* docs(README): clarify Go and Ubuntu requirements on separate lines
Copy file name to clipboardExpand all lines: docs/architecture/architecture.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@
21
21
22
22
The OS Image Composer is a tool for creating customized OS images from pre-built packages. It takes an image template file (YAML) as input and produces bootable OS images in raw or ISO formats suitable for deployment on bare metal systems, virtual machines, and edge devices.
23
23
24
-
The tool uses a layered configuration approach: OS-specific default templates provide base settings for supported distributions (Azure Linux, Edge Microvisor Toolkit, and Wind River eLxr), which are merged with user-provided image templates to generate the final image specification. This approach simplifies the process by handling OS-specific details automatically while allowing full customization when needed.
24
+
The tool uses a layered configuration approach: OS-specific default templates provide base settings for supported distributions (Azure Linux, Edge Microvisor Toolkit, Wind River eLxr, Ubuntu, and Red Hat-compatible distributions), which are merged with user-provided image templates to generate the final image specification. This approach simplifies the process by handling OS-specific details automatically while allowing full customization when needed.
25
25
26
26
Pre-built packages are fetched securely from distribution-specific remote repositories over HTTPS, with automatic dependency resolution and GPG signature verification. The tool maintains local caches for both packages and reusable chroot environments to optimize build performance across multiple image builds.
27
27
@@ -57,7 +57,7 @@ The **Provider** component takes data from **Config** as its input, then orchest
57
57
58
58
### Provider
59
59
60
-
The Provider component is the orchestrator of the image build process. Each supported operating system (Azure Linux, EMT, eLxr) has its own provider implementation that understands the specific requirements and package management for that OS.
60
+
The Provider component is the orchestrator of the image build process. Each supported operating system (Azure Linux, EMT, eLxr, Ubuntu, RCD) has its own provider implementation that understands the specific requirements and package management for that OS.
61
61
62
62
**Provider Interface:**
63
63
-`Init(dist, arch string)` - Initialize the provider with distribution and architecture
@@ -71,6 +71,8 @@ The provider encapsulates all OS-specific logic while maintaining a consistent i
71
71
-**Azure Linux** (azl3) - RPM-based distribution
72
72
-**Edge Microvisor Toolkit** (emt3) - Specialized edge OS
73
73
-**eLxr** (elxr12) - Wind River embedded Linux
74
+
-**Ubuntu** (ubuntu24) - Debian-based distribution
75
+
-**RCD** (rcd10) - Red Hat-compatible distributions
1.**Load Configuration** - Load global configuration and command-line overrides
55
55
2.**Load and Merge Templates** - Parse user image template and merge with OS-specific default template for the image type and architecture
56
-
3.**Initialize Provider** - Select the appropriate provider (Azure Linux, EMT, eLxr) based on template target (OS, distribution, architecture)
56
+
3.**Initialize Provider** - Select the appropriate provider (Azure Linux, EMT, eLxr, Ubuntu, RCD) based on template target (OS, distribution, architecture)
57
57
4.**PreProcess** - Provider validates template and prepares the build environment
58
58
5.**BuildImage** - Provider executes the complete image build pipeline
59
59
6.**PostProcess** - Provider performs cleanup and generates SBOM
@@ -225,7 +225,7 @@ This reuse significantly improves build performance, especially when building mu
225
225
- Generate verification metadata
226
226
- Store signature information in image metadata
227
227
228
-
Image signing is optional and is only performed if configured in the template. See [Understanding Templates](./os-image-composer-templates.md#security-configuration) for signing configuration examples.
228
+
Image signing is optional and is only performed if configured in the template. See [Understanding Templates](./os-image-composer-templates.md) for template configuration details.
0 commit comments