Rocky Linux 10 Tutorial / BaseOS, AppStream, CRB and EPEL repositories
BaseOS and AppStream of Rocky Linux 10 are the primary repositories supplying the operating system and application software, CRB (CodeReady Builder) supplies additional development and dependency packages, while EPEL (Extra Packages for Enterprise Linux) supplies additional packages through the Fedora project. Therefore, CRB and EPEL should be prepared only when necessary, and repository source, signature key, and activation status should be checked and managed.
Distinguish by role and provider first rather than repository name
A repository is a package source that the DNF package manager searches for installation candidates and dependencies. Adding a repository changes not only the search results but also the range of packages that can be selected for future installation and updates. Rather than activating multiple repositories at once just because a package does not appear in the search, first check the required packages and sources.
| Repository | Main Role | ID and Default State of Rocky Linux 10 |
|---|---|---|
| BaseOS | Core components that make up the base operating system | baseos · Active |
| AppStream | User-space applications, runtimes, databases, etc. | appstream · Active |
| Extras | Additional features of Rocky and some external repository configuration packages, etc. | extras · Active |
| CRB | Additional development and dependency packages from the Code Ready Builder series | crb · Inactive |
| EPEL | Extra Packages for Enterprise Linux: Additional packages provided by the Fedora project | After setting installation, epel, etc., are created. |
The distinction between BaseOS and AppStream content is explained in RHEL 10 software distribution documentation, and the actual Rocky repository IDs and default activation status are confirmed based on Rocky Linux repository documentation . The CRB name for Rocky Linux 10 is crb, and we do not use powertools from the old Rocky 8 example as-is.
EPEL is not a repository that forcibly updates the programs in the default repositories to the latest version. Introduction to Fedora EPEL 10 explains that it aims to provide additional supply without interfering with or replacing default packages. However, it does not guarantee the combination of all external repositories or the behavior of each program, and the dependencies and supply policy of the required packages are judged separately.
Record the current activation status and settings before making changes.
The recorded source lab environment was Rocky Linux 10.2 minimal installation VM, DNF 4.20.0, and dnf-plugins-core 4.7.0. Commands are executed from the administrator account of the Rocky guest, and the procedures for a new installation are not applied as-is to production servers already using EPEL.
cat /etc/rocky-release
dnf --version
dnf repolist --enabled
dnf repolist --all
rpm -q dnf-plugins-core epel-release
dnf config-manager --help
--enabled shows the currently used repositories, while --all shows even inactive repositories. This VM had only baseos, appstream, and extras active, CRB was inactive, and epel-release was not installed. Since a non-zero exit status may occur when querying for uninstalled packages, interpret it along with the message.
config-manager is the configuration plugin command for DNF 4. If the command does not exist, verify the installation plan of sudo dnf install dnf-plugins-core from the default repository and prepare accordingly. It was already installed on this VM. Do not mix the different syntax of DNF5 without checking the version.
Configuration files are located in /etc/yum.repos.d/. Copy the original to a separate location before editing. The command below creates a new backup directory and logs the output path.
BackupDir=$(sudo mktemp -d /root/repo-backup.XXXXXX)
sudo cp -a /etc/yum.repos.d "${BackupDir:?Backup directory creation failed}/"
printf 'backup=%s\n' "$BackupDir"
Only continue after the backup command succeeds. This backup records the initial configuration for comparison with later changes. Do not use restoration commands that overwrite the entire directory after another administrator has modified it. Record both the package installation status and activation status so that only the necessary items can be restored.
After enabling CRB, check the installation plan again.
The Rocky documentation advises that when using EPEL, CRB should be prepared because some EPEL packages depend on packages from CRB. If additional packages needed on a new server have been identified, activate them as follows.
sudo dnf config-manager --set-enabled crb
dnf repolist --enabled
dnf info epel-release
sudo dnf --assumeno install epel-release
config-manager --set-enabled saves the configuration, so it remains active even after the command ends. The config-manager reference describes persistent configuration changes. These differ from the per-command --enablerepo option used later.
In this exercise, the supplier repository for epel-release was extras. A pre-check with CRB turned off showed only one configuration package, but when CRB was turned on, the actual installation plan included 3 packages, including additional SELinux policy packages. Do not use the plan before changing the repository as the basis for approval; instead, read the latest plan after enabling CRB.
--assumeno denies installation without approval, so Operation aborted. can be expected. Distinguish between failures caused by errors and intentional denials, and review the list of installations, upgrades, removals, and repositories. If the conditions are right for actual changes, install with the following command.
sudo dnf install epel-release
rpm -q epel-release
rpm -ql epel-release
dnf repolist --all
Read the plan again, approve it, and then check if the setup package and repository items have appeared. On this VM, epel-release-10-7.el10_1.noarch and CRB's selinux-policy-extra, selinux-policy-targeted-extra have been installed. Do not judge the operating system as 10.1 just by the el10_1 string in the package release name.
epel is active, and epel-testing ·debug· source repositories were inactive. Do not enable testing for regular exercises or activate all repositories at once. If the installation appears to be interrupted, check the actual state of the packages, configuration files, and DNF history before repeating the same task.
Check the EPEL signing key and verification settings.
epel-release provides repository configuration and public signing key files. The fact that the key file exists, that a trusted key is registered in the RPM key database, and that the downloaded package's signature has been verified are different things. First, read the keys and verification options specified in the configuration.
dnf config-manager --dump epel | grep -E '^\[|^enabled =|^gpgcheck =|^gpgkey =|^metalink =|^sslverify ='
gpg --batch --show-keys --with-fingerprint /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-10
The above filter only displays the necessary configuration items. The source lab confirmed package signature verification gpgcheck = 1, HTTPS certificate verification sslverify = 1, and checked the EPEL 10 key path. If the gpg command does not exist, review the installation plan for sudo dnf install gnupg2 from the default repository and prepare accordingly. Do not disable signature verification or HTTPS certificate verification to view the key.
The full fingerprint of the EPEL 10 key is compared with the EPEL 10 entry on the official Fedora security page . The value confirmed by reading the key file in this exercise is as follows.
7D8D 15CB FC4E 6268 8591 FB26 33D9 8517 E37E D158
Since the official key may be replaced in the future, do not blindly trust the value written in posts; compare it with the current official page. When installing actual EPEL packages, if key import approval is requested, verify the source and full fingerprint before approving. Do not approve solely because the short key ID looks similar or skip to --nogpgcheck.
The EPEL package examples in this course only go up to the information lookup and installation plan verification in the next section. Although the fingerprint of the key file was verified, htop was not actually installed or executed, so this does not extend to verifying its runtime compatibility or the signature verification result during package installation.
Check the repository metadata and individual package sources.
When you add a repository, do not just look at the name but also check the actual configuration file and the linked source.
dnf repoinfo epel
dnf --disablerepo='*' --enablerepo=epel info htop
The first command shows the status, metadata timestamp, metalink, mirror URL, and configuration file location. The metalink is the source address used to find the mirrors and repository metadata information. The second command checks the htop candidate from EPEL while excluding other repositories for this query only. The '*' enclosed in single quotes prevents the shell from expanding it to a filename in the current directory.
On this VM, candidates Repository: epel and htop-3.3.0-5.el10_0.x86_64 were displayed. This does not indicate that the installation is complete. Also, directly applying this query method that disables all other repositories to the actual installation command requiring dependency packages may not resolve issues.
EPEL 10 also uses a supply structure based on minor versions. Check the result of variables and metalink from epel.repo using repoinfo, and compare it with the OS release and the support range for the required packages. Do not hard-code a different release URL merely because a particular 10.x directory appears. Rocky also connects the default releasever path to the latest supply within the major release, so before binding a server to arbitrary past repositories, confirm the distribution’s version policy and update plan.
In the recorded source lab’s EPEL mirror list on Rocky Linux 10.2, paths for 10.3 were also visible. Therefore, we did not conclude that all EPEL programs are compatible with 10.2 execution solely based on successful access and dependency plan verification. If the combination of operating system and repository support is unclear, defer program installation and first check the official support scope of the current distribution and EPEL, as well as any necessary updates.
Distinguish between permanent deactivation and one-time use.
If you continue to operate additional packages, you must also maintain the update paths for EPEL and the required CRB. In this exercise, we did not install packages from EPEL, and since the purpose is to revert any changes in activation status, we turn them off as follows. This command does not indiscriminately turn off repositories already used on other servers.
sudo dnf config-manager --set-disabled epel
sudo dnf config-manager --set-disabled crb
dnf repolist --enabled
dnf repolist --all
The actual result was that only the original baseos, appstream, and extras were returned to active status. Deactivation does not delete repository settings or installed packages. In this VM, epel-release and additional SELinux policy packages remain. If subsequent updates for these packages are necessary, a plan should be made to reuse the relevant repositories.
If you want to use EPEL and CRB in a single command without changing the permanent settings, you can specify it as follows. The default repositories are used as they are, and only the two additional repositories are allowed for this command.
sudo dnf --enablerepo=epel,crb --assumeno install htop
dnf repolist --enabled
rpm -q htop
In the practice plan, a total of three packages appeared: htop from EPEL and hwloc-libs·ocl-icd from BaseOS. After ending with a rejection, htop was still not installed, and EPEL·CRB did not reappear in the normal repolist --enabled. This difference confirmed that a one-time option is different from being permanently enabled.
If you decide to keep it enabled, explicitly save it to sudo dnf config-manager --set-enabled crb and sudo dnf config-manager --set-enabled epel and check the status again. When restoring to the original settings, compare only the changed items; in this practice, it was also confirmed that the existing Rocky repository files matched those before the change and that SSH·SELinux Enforcing was maintained.
Distinguish and resolve repository issues.
| Observed phenomena | Judgment and action |
|---|---|
| CRB is not in the list. | Start by checking the operating system, major version, and basic repository configuration packages. Do not guess and add repository IDs from other distributions. |
| The config-manager command is missing. | Check the DNF version and whether dnf-plugins-core is installed. |
| Even after installing epel-release, the desired package is not available. | Check the exact name, architecture, major version of EPEL, active status, and actual availability. Do not mix EPEL 9 packages with Rocky 10. |
| metalink or mirror connection failure. | Check DNS, network, time, proxy, and source issues. Do not hide problems by turning off TLS verification. |
| Key fingerprint or source is different from expected. | Without approving installation, compare with the latest official keys and repository settings. |
| The repository was disabled, but the program remains. | This is a normal difference. Manage installation status, dependencies, and future update paths separately. |




