Choosing Ubuntu, Debian, Fedora, Rocky Linux, or AlmaLinux

1. Choose for the workload, not the logo

All five distributions can teach Linux fundamentals. The meaningful differences appear in package management, release cadence, defaults, vendor or community support, security policy, documentation, cloud images, and how closely the lab resembles a target production environment.

2. The five distributions belong to two main families

flowchart TB
  L["Linux kernel and upstream projects"] --> D["Debian family"]
  L --> R["Red Hat family"]
  D --> DEB["Debian"]
  D --> UBU["Ubuntu"]
  R --> FED["Fedora"]
  R --> ENT["Enterprise-compatible ecosystem"]
  ENT --> ROC["Rocky Linux"]
  ENT --> ALM["AlmaLinux"]
  DEB --> APT["deb packages and APT"]
  UBU --> APT
  FED --> RPM["RPM packages and DNF"]
  ROC --> RPM
  ALM --> RPM

The family distinction matters because package names, package managers, repository configuration, default security controls, and some file locations differ. Core concepts—processes, permissions, systemd, TCP/IP, filesystems, SSH, and Bash—transfer across both families.

3. Operational profiles

4. Release cadence changes operational risk

“Stable” does not mean unchanged. Supported distributions still deliver security updates and selected bug fixes. The difference is how aggressively feature versions and interfaces move during the release lifetime.

5. A practical selection matrix

6. Inspect a candidate image before committing

After booting any candidate, collect the facts that affect course compatibility. These commands are read-only.

printf '=== identity ===\n'
cat /etc/os-release
uname -srmo

printf '\n=== package tooling ===\n'
for tool in apt apt-get dpkg dnf rpm; do
  if command -v "$tool" >/dev/null 2>&1; then
    printf '%-8s %s\n' "$tool" "$(command -v "$tool")"
  fi
done

printf '\n=== init and security ===\n'
ps -p 1 -o pid,comm,args
command -v systemctl || true
command -v getenforce >/dev/null && getenforce || true
command -v aa-status >/dev/null && aa-status 2>/dev/null | head || true

printf '\n=== architecture and virtualization ===\n'
uname -m
systemd-detect-virt 2>/dev/null || true

Do not infer the distribution from the kernel version alone. Cloud and container images may run a kernel supplied by the host while presenting a different user-space distribution.

7. Hands-on lab: write a distribution decision record

Create a short, version-controlled decision record rather than silently choosing a platform. The example recommends Ubuntu LTS as the primary lab and an enterprise-compatible distribution as the secondary lab; change the values when your production target differs.

lab="$HOME/devops-academy/linux/chapter02/lesson01"
mkdir -p "$lab"
cd "$lab"

cat > distribution-decision.md <<'EOF'
# Linux Lab Distribution Decision

## Decision
- Primary lab: Ubuntu LTS
- Secondary compatibility lab: Rocky Linux or AlmaLinux

## Required capabilities
- systemd and journalctl
- A package manager with signed repositories
- SSH server support
- Snapshots or exportable machine state
- x86_64 or ARM64 compatibility with the host

## Reasons
- Stable, supported primary environment for reproducible lessons
- Broad documentation and cloud-image availability
- Secondary RPM/DNF and SELinux practice

## Risks and mitigations
- Distribution-specific commands: label commands by family
- Package-version differences: record versions in lab reports
- Lifecycle expiration: review support status before each major chapter

## Review trigger
Review this decision when the target production platform changes or the
selected release approaches end of support.
EOF

cat distribution-decision.md

8. Common selection mistakes

9. Knowledge check

10. Summary

Distribution choice is an operational design decision. Ubuntu LTS and Debian stable provide predictable Debian-family labs; Fedora emphasizes current technology and regular upgrades; Rocky Linux and AlmaLinux provide enterprise-compatible RPM/DNF and SELinux experience. Use one primary platform for depth and a second family for transferability.

11. Further reading

• Ubuntu release-cycle and lifecycle documentation — LTS and interim release policies.
• Debian Releases — stable, testing, unstable, and release support information.
• Fedora Release Life Cycle — release cadence, maintenance, and end-of-life policy.
• Rocky Linux documentation — release notes, installation, and enterprise-family administration.
• AlmaLinux release notes and lifecycle documentation — supported major and minor releases.