⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
azldev
Read this before running azldev or editing azldev config, and whenever working in a repo that contains an azldev.toml file; do not guess azldev's commands or config. Explains how to use the azldev CLI to build a distro from TOML config, including the core concepts (components, overlays, distros, rendered specs, locks), running azldev (repo root or -C, plus the -q and -O json flags), the common commands, and where to go for each workflow. Triggers include azldev, comp build, comp render, comp update, build a component, add a component, distro config.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
An open-source Linux distribution built and optimized for Azure, with sources derived from Fedora Linux. Azure Linux provides a secured, reliable operating system for virtual machines, containers, and bare-metal platforms.
Azure Linux is built on a robust open-source foundation from the Fedora ecosystem and enhanced with Azure-specific innovations. This provides the familiarity of the RPM package ecosystem, while adding Azure-native security, compliance, and operational capabilities.
Key features of Azure Linux include: hardened security posture, an Azure-optimized kernel, supply chain security, native Azure integration, and a predictable lifecycle.
This branch holds the in-development sources for Azure Linux 4. For Azure Linux 3, see the
3.0branch.
Getting started
The links below will help you get started with Azure Linux:
| Product documentation | https://aka.ms/azurelinux |
| Release information | GitHub Releases |
| File a bug / feedback | GitHub Issues |
| Ask a question / get help | SUPPORT.md |
| Get started as a distro developer | DEVELOPING.md |
| Contribution guidelines | CONTRIBUTING.md |
| Report a security issue | SECURITY.md |
Using Azure Linux
Note: Azure Linux 4 is still in development
To try Azure Linux in an Azure VM, please visit our Azure Linux 4.0 page on the Microsoft Marketplace.
To try Azure Linux base container, please use the following image reference: mcr.microsoft.com/azurelinux-beta/base/core:4.0
To try Azure Linux in a local VM, please download the ISO Installer: x86_64 / ARM64
Before using a downloaded ISO, verify the checksum and signature of the ISO.
After downloading and verifying the ISO, follow the ISO installer instructions to install and use Azure Linux in a local VM (Hyper-V on Windows or QEMU/KVM on Linux). The ISO runs the Anaconda installer.
Note: Support for the ISO is community based. Before filing a new bug or feature request, please search the list of Github Issues. If you are unable to find a matching issue, please report new bugs by clicking here. For additional information, refer to the SUPPORT.md file.
To try Azure Linux on the Windows Subsystem for Linux, please download the .wsl distribution package for your architecture:
Before installing a downloaded package, verify the checksum and signature of the .wsl package.
Install the distribution using wsl:
wsl --install --from-file "C:\Path\To\AzureLinux-4.0-ARCH.wsl"
To list all the installed distributions:
wsl --list
To use the distro:
wsl -d AzureLinux-4
What's in this branch?
Azure Linux 4 is an RPM-based distribution optimized for Azure and modern cloud workloads. It is defined by a set of TOML configuration files and targeted overlays applied to Fedora Linux, its upstream base.
Deviations from upstream are declaratively defined and scoped to avoid unnecessary divergence or forking. This repository contains a mechanically rendered set of RPM package spec files derived from applying this layer to Fedora's upstream packaging sources.
How Azure Linux is defined
The distro is described almost entirely in TOML-based configuration files. Our open-source development tool, azldev, is used to apply this configuration to upstream Fedora spec files and packaging sources.
azldev.toml # Top-level entry point
├── distro/ # Distro-wide configs (e.g., sources, mock configs)
└── base/ # The "base" project: components, images, tests
└── comps/ # Component definitions (one per source package)
└── images/ # Base image definitions
Concepts/terms
- Components (also known as source packages) are the unit of packaging. Most are imported in source form from Fedora's upstream dist-git repositories; each component produces one or more RPMs. Azure Linux builds all components from sources to produce a full set of installable RPM packages.
- Overlays are declarative modifications to upstream specs and sources
(e.g., patches, additions/removals, build parameters). They live alongside the component definition and always carry a
descriptionexplaining why the change is needed. Overlays let us avoid forking upstream specs and are more flexible than plain textual patches. - Rendered specs are the final
.specfiles produced by applying overlays to upstream sources. They are mechanically generated byazldev, checked in for visibility and auditability, and live underspecs/. Treat them as derived output and not sources for editing. We use them as the input to standard RPM building services/tools (mock+rpmbuild,koji).
For a deeper tour of the tooling, the overlay system, and how to get started developing within this distro, please see DEVELOPING.md.
Repository layout
| Path | What's there |
|---|---|
azldev.toml | Top-level config — includes distro/ and base/. |
distro/ | Distro definitions (Azure Linux + upstream Fedora), shared mock configs. |
base/ | The base project: components, images, tests. |
base/comps/ | Component definitions — the heart of the distro. |
base/images/ | Image definitions (VM, container, etc.) built from the component set using KIWI NG. |
specs/ | Rendered specs — generated .spec files after overlays are applied. Checked in for visibility; do not hand-edit. |
locks/ | Per-component lock files pinning upstream commits + input fingerprints; do not hand-edit. |
external/schemas/ | Cached copy of the JSON Schema for TOML config files; mirrored from azldev. |
.github/ | CI workflows, plus Copilot prompts, skills, and agent instructions used by AI-assisted development. |
Getting started as a distro developer
If you want to build or develop within the distro, start with DEVELOPING.md. Don't worry about this if you're primarily looking to use the distro.
Engagement & support
- Bugs and feature requests: file a GitHub issue. Please search existing issues first to avoid duplicates. Share as much as you can with us regarding what you tried and what you're seeing.
- Support: see SUPPORT.md for the full set of channels.
- Security vulnerabilities: do not open a public issue. Follow the process in SECURITY.md to report privately to the Microsoft Security Response Center.
- Pull requests: see [CONTRIBUTING.md](CONTRIBUTING
// HOW IT'S BUILT
KEY FILES