How stratos-linux/gnome-iso works
Project type and purpose
• This is an open-source ISO-builder tool for Arch-based distributions (“StratOS iso”).
• Its purpose is to assemble a bootable ISO containing a customized Arch Linux system, including theming, default configs, and installer integration.
File structure
• Top-level
• .github/workflows/deploy.yml → CI pipeline that invokes the build
• .gitmodules → external submodules (e.g., installer configs)
• README.md, LICENSE
• airootfs/ (the overlay root filesystem)
• etc/ → system defaults (grub, pacman, networkd, systemd services, dconf profiles, user skeletons)
• root/ → root-user defaults (automation scripts, SSH keys)
• usr/
– lib/systemd/system → custom service units
– local/share/livecd-sound → sound config
• (Implicit) build.sh or similar script at repo root that drives archiso
README for additional insights
• Uses Arch’s official archiso package to assemble the ISO
• Build process: clone + ./build.sh → ISO for VM or bare metal
Main components & interactions
a. Components
1. GitHub Repository
– Source of build scripts, airootfs overlay, submodules
2. CI/CD Runner (GitHub Actions)
– Executes deploy.yml → checks out code, calls build.sh
3. Host Environment
– Must have archiso installed
– Runs build.sh either locally or within CI
4. archiso Toolchain
– Stage 1 (bootstrap) & Stage 2 (chroot + overlay)
– Consumes airootfs/ directory and pacman.conf, mkinitcpio.conf, hooks
5. airootfs Overlay
– Merges etc/, usr/, and root/ on top of a base Arch filesystem
6. Git Submodules
– Additional configs (e.g., Calamares installer, kernel hooks)
7. Output ISO Artifact
– Bootable ISO image, packaged with GRUB, systemd, theming, installer
8. Target Environment
– VM or bare-metal installer consuming the ISO
b. Data flows / relationships
• Developer pushes code → GitHub Repo
• Push event triggers CI/CD Runner → checks out code + submodules
• CI/CD or local Host Env launches archiso via build.sh
→ archiso builds in two stages:
• Stage 1: bootstrap minimal base
• Stage 2: chroot + overlay using airootfs
• Applies pacman hooks, mkinitcpio, custom systemd units, themes
• archiso outputs final ISO → stored as CI artifact or local file
• ISO is downloaded/deployed to VM/bare metal
c. Architectural patterns & design principles
• Overlay pattern: airootfs acts as a drop-in overlay onto Arch base
• Infrastructure-as-code: all system configs live in Git, reproducible build
• Micro-phases: separate bootstrap vs. chroot phases in archiso
d. Key technologies/frameworks
• archiso (Bash, rsync, mkarchiso)
• pacman (package manager config & hooks)
• mkinitcpio (initramfs generators)
• systemd (service unit overlays)
• dconf (desktop settings)
• GRUB (bootloader theming)
• GitHub Actions (CI/CD)
• Git submodules (external config bundles)