Repository Architecture
RLC Pro AI delivers packages through a layered repository architecture managed by the CIQ Depot CLI. This page explains which repository each part of the stack comes from, which matters when you are auditing package provenance, mirroring content, or troubleshooting an update.
All repositories are hosted on CIQ infrastructure and accessed through authenticated connections. RLC Pro AI shares the general repository model of the RLC Pro family, described in the RLC Repository Architecture guide; this page covers what is specific to the AI product.
sudo depot enable rlc-ai-9. A freshly deployed image shows only the public ciq-depot-client repository until you enable the product. See the Post-Installation Guide.Repository Layout
These are the repositories enabled by default on an entitled RLC Pro AI 9 system, with their DNF priorities. Lower priority numbers win, so CIQ AI packages take precedence over Rocky base packages when both carry the same name:
| Repository | Contents | Priority |
|---|---|---|
rlc-9-ai | The AI userspace built by CIQ: PyTorch, TorchVision, ONNX, SLEEF, supporting Python libraries, and the RLC Pro AI release packages | 20 |
ciq-kernel-lt-6_12-el9 | The CIQ Linux Kernel (CLK) 6.12 long-term series and matching NVIDIA open kernel modules (kmod-nvidia-dc-open*) | 20 |
rlc-9-core | CIQ core packages, including the NVIDIA data center driver userspace (nvidia-dc-driver*) and foundational CIQ enhancements | 50 |
rlc-9-supplemental | The accelerator toolkits: NVIDIA CUDA Toolkit component packages, AMD ROCm packages, nvidia-container-toolkit, and other CIQ-provided utilities | 99 |
rocky-9-baseos, rocky-9-appstream, rocky-9-extras | Upstream Rocky Linux packages | 99 |
ciq-depot-client | Public repository for the Depot CLI | 99 |
Additional Rocky repositories (CRB, High Availability, SAP, and others) plus source and debug variants of everything above are configured but disabled by default. List them all with:
sudo dnf repolist all
Where the AI Stack Comes From
A practical map of the components you are most likely to care about:
| Component | Package(s) | Repository |
|---|---|---|
| PyTorch / TorchVision | python3-torch, python3-torchvision | rlc-9-ai |
| CIQ Linux Kernel | kernel-*-el9_clk | ciq-kernel-lt-6_12-el9 |
| NVIDIA kernel modules (open) | kmod-nvidia-dc-open* | ciq-kernel-lt-6_12-el9 |
| NVIDIA driver userspace | nvidia-dc-driver*, Fabric Manager, IMEX, persistenced | rlc-9-core |
| CUDA Toolkit | cuda-* | rlc-9-supplemental |
| AMD ROCm | rocm-* | rlc-9-supplemental |
| Container GPU support | nvidia-container-toolkit | rlc-9-supplemental |
You can verify the origin of any package yourself:
sudo dnf repoquery --qf "%{name} -> %{reponame}\n" python3-torch nvidia-dc-driver580-cuda
Architectures
All CIQ repositories for RLC Pro AI are published for both x86_64 and aarch64, with source and debug variants available. List the full set for the product with:
sudo depot list rlc-ai-9
The product also includes rlc-9-ai-images (installation and cloud images) and rlc-9-ai-oci-images (container images) repositories, which serve the artifacts described in Getting Started.
GPG Keys
RLC Pro AI packages are verified against two signing keys:
| Key | URL | Used By |
|---|---|---|
| CIQ Signing Key V2 | https://ciq.com/keys/rpm-gpg-key-ciq | rlc-9-ai, rlc-9-core, rlc-9-supplemental, ciq-kernel-lt-6_12-el9 |
| Rocky Linux 9 | https://download.rockylinux.org/pub/rocky/RPM-GPG-KEY-Rocky-9 | All rocky-9-* repositories |
Package signature verification (gpgcheck) is enabled on all repositories. The first DNF transaction after enablement prompts you to import the CIQ key.
Air-Gapped and Offline Environments
For environments without direct access to depot.ciq.com, the entitled repositories can be mirrored to internal infrastructure with reposync or rsync, and the container images can be mirrored to a local registry. See the CIQ Depot how-to guides for reposync and rsync, and the Depot container guide for pushing images to a local registry.
Repository Access Is Root-Only
The Depot-generated repository configuration embeds authentication credentials and is readable only by root. A regular user running dnf repolist sees only the public ciq-depot-client repository. This is expected behavior, not a broken enablement; use sudo for repository operations.
Keeping Configuration Current
The repository definitions in /etc/yum.repos.d/depot-rlc-ai-9.repo are generated by the Depot CLI. Do not edit the file by hand: changes are overwritten by depot refresh, which a systemd timer runs automatically every 7 days.
systemctl list-timers depot-refresh.timer