Rocky Linux 10 Tutorial / Minimal installation and the first administrator login
The minimal installation of Rocky Linux 10 proceeds by booting a dedicated VM with a verified ISO, selecting the installation disk, a regular administrator account, and the minimal installation profile. Once installation is complete, boot from the virtual disk instead of the ISO, and verify the login of the regular account and sudo permissions. The example uses a Rocky Linux 10.2 minimal ISO and a dedicated VM in VirtualBox 7.2.10. Installer wording depends on the selected language and minor release; match each control to its purpose.
Before installation, verify the ISO and target VM first
As created in Virtual Machine Setup Tutorial , use a VM separated from operational data. This practice VM used 2 CPUs, 4GB of memory, EFI, and one 40GiB virtual disk. If you are not sure whether you can erase existing disks, do not start the installation.
Check the VM name in VirtualBox and the VDI or ISO connected to the storage. The installation target is a dedicated virtual disk like system.vdi, and the installation media is the verified Rocky-10.2-x86_64-minimal.iso. Use a file that has passed ISO signature and checksum verification .
This ISO is intended for installing a minimal server. After installation, it is normal for the desktop not to appear and for a text login screen to be shown. There is no need to add a GUI desktop package to follow the screen.
Proceed to the installation summary after performing the media check.
- Start the VM and in the installation menu select Test this media & install Rocky Linux Minimal 10.2 . Even if the file has passed verification, this step can be used to check for installation media read errors.
- If there are no errors in the media check, the installation screen will appear. Select the installation language to use and select Continue.
- Check the items with warnings first in Installation Summary . Review the installation destination, user creation, installation source, and software selection.
If the check fails, do not force the installation. Verify the ISO hash, file read errors, and the connected media. Issues like CPU requirement errors or not reaching the installation menu should be investigated separately for host/virtual CPU conditions, distinct from file integrity.
The source lab used Korean installer text; the corresponding control names are described here in English. The screen language and keyboard layout may differ. Check the keyboard indicator at the top right and the keyboard entry, and make sure the characters you use for the username and password are entered as intended. Do not expose secret values in a plain text editor or screen sharing for password verification.
Select the installation disk and software.
Open Installation Destination and check the device model and total capacity. On the exercise screen, we compared a single virtual disk of 40GiB, ATA VBOX HARDDISK, sda. The device name in a real environment may differ, so do not select it based solely on the name sda.
- Make sure the dedicated disk you want to use is checked. Do not select unnecessary additional disks.
- On the first empty practice disk you create, select automatic storage configuration. Do not apply this example as is if it is a server where existing data must be preserved or if a separate partition policy exists.
- Press Done to return to the summary screen. If a window appears requesting the reclamation or deletion of existing space, double-check the target and its impact.
- In Software Selection, make sure that minimal installation is selected. Instead of adding multiple services at once, install only the required packages and manage them individually.
After planning automatic partitions, the remaining space on the screen may appear smaller than the total capacity. The total disk size, already planned partitions, and remaining space are different values. Check the actual creation results in lsblk and findmnt after installation.
Set the timezone according to the actual operating region in Time and Date. For this practice managed in Korea, use Asia/Seoul. In Network and Host Name, check that the adapter of the installation VM is connected. In the first practice using NAT, start with a DHCP address, and configure a static IP separately after securing the recovery console, as it is easier to understand the sequence.
The roles of all installation items can be checked in Rocky Linux Official Installation Guide. Since the ISO example version in the guide and the actual installation version may differ, compare based on the items and selection results on the actual 10.2 screen.
Prepare a regular administrator account instead of root.
Root is a privileged account that manages the entire system. Rocky Linux 10 Installation Program Changes explains that the root account is disabled by default and a regular administrator account is created. If you do not grant administrative permissions to the regular account while root is disabled, managing the system after installation may become difficult.
- Open Create User and enter the name to display and the username for login. The account name for this exercise is
lfstudent. - Check the Add administrative privileges with this user account (wheel group member) item. The wording on the screen may vary depending on the translation status, but the key is to make this account an administrator in the wheel group.
- Set it so that a password is required to log in, and create a sufficiently long password that only you know. The account name in the text is an example, and no public passwords are provided.
- After completion, check on the summary screen that a regular administrator has been created and that the root account is deactivated as intended.
Before starting installation, check five items together in the summary: the dedicated disk, minimal software profile, time zone, connected network and enabled administrative account. Resolve warnings before proceeding.
The wheel group is used to grant administrative privileges, and sudo is the tool used to execute allowed administrative commands. We will not only check the selections on the installation screen but also verify the actual permissions at first login.
Start the installation and reboot to the virtual disk.
After checking all necessary items on the summary screen, press Begin Installation. From this point, partition configuration, formatting, and package installation may proceed. Do not forcibly turn off the VM or disconnect the disk before completion. Do not repeatedly send installation commands to the same VM because the process takes a long time.
After installation completes, use the installer’s reboot action. If the installation ISO boots again, do not start the installation again; boot from the installed virtual disk instead. Check the ISO connection on the optical drive and the boot order, and if necessary, shut down the VM normally and then disconnect the ISO. This is different from deleting or detaching the installed disk file itself.
After reboot, when the text login prompt appears, log in with the regular account created during installation. It is normal that characters do not appear on the screen when entering the password. Do not type the same password repeatedly thinking it was not entered; enter it once and then press Enter.
Check the version, permissions, and disk at first login.
The following commands are executed inside the Rocky Linux VM terminal. Do not run them in Windows PowerShell to avoid mixing results with the host. These commands inspect system state, and sudo -v verifies whether the account can perform sudo authentication.
cat /etc/os-release
whoami
id -nG
sudo -v
lsblk -o NAME,SIZE,FSTYPE,MOUNTPOINTS
findmnt /
ip -br address
ip route
getenforce
| Items to check | Judgment criteria |
|---|---|
| Distribution | Check ID=rocky and installed VERSION_ID |
| General Account | Check if the account name created in whoami is displayed |
| Administrative Privileges | Check if wheel is included in id -nG and confirm sudo -v success |
| Storage | Check the connection of dedicated virtual disk and root file system, and verify actual partition configuration |
| Network | Check the adapter address other than loopback and the default route. NAT address may vary depending on the environment |
| SELinux | In exercises maintaining the default policy, verify that the state is Enforcing. Do not turn it off arbitrarily to resolve connection issues |
In the source lesson’s November 12, 2026 lab, these commands were run after booting Rocky Linux 10.2 with the kernel 6.12.0-211.16.1.el10_2.0.1.x86_64 for the first time. The recorded checks confirmed lfstudent wheel group membership and sudo authentication success, the root file system’s XFS, the address and default route of enp0s3, and the SELinux Enforcing status. These are results from Rocky Linux running inside VirtualBox, not from commands on a Windows host.
At this time, lsblk showed a 40G disk with 600M for EFI, 2G for /boot, and the rest used as an LVM area. LVM (Logical Volume Manager) is a method that manages disk space by dividing it into logical volumes. That automatic partition layout allocated about 33.5G to rlm-root and about 3.9G to rlm-swap. Do not memorize these numbers as fixed results for every installation; instead, compare with your own output and mount points. findmnt / confirmed that the actual root path was linked to /dev/mapper/rlm-root.
If a message about insufficient permissions appears, check whether the administrator check was missed during installation. First, determine if there is a usable recovery path, such as a root password or another administrator account, and do not arbitrarily overwrite the entire sudo configuration file. For a fresh practice VM immediately after installation, reinstalling with the correct account setup can be considered, but this should not be applied to systems with existing data.
Even if you successfully log in for the first time, it does not mean that the preparation for operating the application is completely finished. The completion criteria in this article are that the installed virtual disk boots up, you can log in with a regular account, and you can explain the intended sudo privileges, network, and file system status.




