Learn Rocky Linux - Pre-Requisites Skill & Setup Environment

#Introduction

Welcome to the Learn Rocky Linux series! This series will guide you to master Rocky Linux — an enterprise-grade, open source, and 100% binary-compatible Linux distribution with RHEL (Red Hat Enterprise Linux) — from installation and lifecycle, package management with dnf5, system services and boot, SELinux and firewall, to bootable containers (bootc), image mode, cloud, and production hardening. There are 23 episodes in total, organized into six phases, starting from prerequisites to production readiness.

But before downloading the ISO or creating the first VM, there are some basic skills and tools you need to prepare. Why are these prerequisites important? Because Rocky Linux is not a desktop distro you can use in a single click. It is an enterprise server operating system managed through the terminal — every decision is made via the CLI, package manager, and text configuration files. If you don't yet understand how the terminal and the Linux system structure work, every command in this series will feel like meaningless incantations.

Imagine wanting to become a pilot without ever studying flight theory. No matter how good the aircraft is — and Rocky Linux is a very reliable aircraft — it is still hard to fly without understanding its instrument panel. This episode 0 is your preparation room: we will make sure the basic skills are in place, prepare the tooling, and then provide the environment that will accompany you throughout the series.

#Basic Skills You Must Master

#Linux CLI and Basic Administration

Rocky Linux is managed almost entirely from the terminal. You must be comfortable with directory navigation (cd, ls, pwd), file manipulation (cp, mv, rm, mkdir), and pipes and redirection (|, >, >>). Also understand how to view and manage processes with ps, top, and kill, because almost all services on Rocky Linux are just processes running in the background.

In addition, get used to the concept of users and permissions: who can read, write, and execute a file. Rocky Linux uses the POSIX permission model (r/w/x for owner, group, and others), which you will explore in depth in episode 6. As a sysadmin, you will face the question "why does this permission deny access?" almost every day — so understand it from now.

#Package Manager and Systemd Concepts

Rocky Linux uses RPM as the package format and DNF as the package manager that manages dependencies. You don't need to master them before this series — episodes 4 and 5 will cover them thoroughly — but first understand the idea: an operating system is not installed per file, but per package that has dependencies, and all of that is managed by the package manager.

Systemd is the init system that manages all services on Rocky Linux. You will encounter systemctl in almost every episode, because services such as SSH, firewalld, and Cockpit are all managed through systemd. Understand the basic ideas of units, targets, and the journal log — the details will be covered in episode 7.

#Server Networking Basics

Finally, understand the basics of networking: what an IP address, subnet, gateway, DNS, and port are. You don't need to be a network engineer, but you must be able to read ip addr output and understand the concept of a service listening on a specific port. Most of this series — firewalld, SSH, TLS, Cockpit, containers — all works on top of these networking concepts.

The good news is, you don't need to master all of that at an advanced level before starting. What's needed is enough of a foundation to not get lost while reading commands and configurations. Each episode introduces concepts gradually, so never hesitate to look up the official documentation when you come across an unfamiliar term.

#Software and Hardware Setup

#Minimum Specifications

Rocky Linux is not a wasteful distro, but a production server needs reasonable resources. The recommended minimum specifications to follow this series:

Choose the "Comfortable" option if possible, because episodes 18-20 about containers and virtualization will run smoother with extra resources. An SSD disk is preferable for a responsive installation and boot experience.

#Virtual Machine or VPS

You have two main paths for your environment. A virtual machine on VirtualBox, VMware, or Proxmox gives you full freedom to experiment — including partitioning, boot, and snapshots that will be used in episodes 3 and 10. A VPS from providers such as DigitalOcean, AWS EC2, Hetzner, or Oracle Cloud is closer to real production conditions, but some features like bootloader access are more limited.

For this series, a local VM is most recommended because you are free to make mistakes and reset the environment at any time. Use a VPS only if you are already confident with the basic concepts.

#Official Rocky Linux Image

Download images only from official sources. For manual installation, use the ISO from the official download page with the Minimal, Boot, or DVD variant. For cloud providers, use the cloud images already optimized for GenericCloud, Oracle Cloud, AWS, Azure, or GCP:

sha256sum Rocky-10.2-x86_64-minimal.iso

Compare the sha256sum output with the checksum value listed on the official download page. A differing value means the file is corrupt or not from an official source — do not continue the installation. Verifying integrity like this is a security habit you should carry throughout your sysadmin career.

#Environment Verification

Before moving on, make sure all core tools are available on your machine by running the verification all at once:

git --version
ssh --version
qemu-system-x86_64 --version
VirtualBox --help

Successful commands will print a version number, not command not found. The same verification also applies to ssh --version as a reminder that your remote access tool must be ready from the start. Tools needed: git for version control, ssh for remote access used from episode 11 onward, and one hypervisor (VirtualBox, VMware, or QEMU/libvirt) to run the VM.

Once the verification passes, make it a habit: create a clean snapshot of the Rocky Linux VM as soon as the installation finishes. This snapshot is a recovery point that will save you many times throughout the series — when an experiment breaks the configuration, you simply restore to the snapshot instead of starting from scratch.

Another discipline to carry from the start: run every command in the terminal yourself, not just copy it. When you type, you notice the options, see the errors, and understand how the system reacts. Reading commands on screen without typing them produces fragile knowledge.

#Learning Plan

So that this 23-episode journey doesn't get confusing, here is the map of its six phases:

• Phase 1 (episodes 0-2): prerequisites, history, and Rocky Linux architecture.
• Phase 2 (episodes 3-7): installation, package management, repositories, users, and systemd.
• Phase 3 (episodes 8-12): storage and LVM, networking, kernel, Cockpit, and logging.
• Phase 4 (episodes 13-16): firewalld, SELinux, SSH, and TLS.
• Phase 5 (episodes 17-20): performance tuning, bootc, KVM, and containers.
• Phase 6 (episodes 21-22): Rocky 10 lifecycle, ecosystem, and final reflection.

Follow the order. Each episode is built on the concepts of the previous one, and skipping a chapter will make the next one feel unfamiliar.

#Closing

In this episode 0, you have laid the foundation for the entire series: understanding basic Linux CLI and administration skills, package manager and systemd concepts, server networking basics, and making sure a VM or VPS with the official Rocky Linux image is ready in your environment.

Key takeaways:

• Rocky Linux is an enterprise server managed through the terminal: master the CLI, users, permissions, and processes.
• Understand the basic ideas of RPM/DNF and systemd before diving into the details in episodes 4-7.
• Prepare a VM with at least 2 vCPU, 2 GB RAM, and 20 GB disk; larger is more comfortable.
• Download the ISO or cloud image only from official sources and always verify the checksum.
• Create a clean snapshot after installation as your experimentation reset button.

In the next episode 1, we will discuss the history, background, and why Rocky Linux is needed — from the CentOS legacy, Red Hat's discontinuation of CentOS Linux, the birth of the Rocky Enterprise Software Foundation, to why 100% binary compatibility is its main selling point. Make sure your environment is ready, because the Learn Rocky Linux journey has just begun!