Using Rocky Linux Module Streams to Install Specific Versions of Software
Learn how to enable, use, and reset DNF module streams on Rocky Linux to get exact versions like Node.js 14, with steps, trade‑offs, and a reset procedure.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to enable, use, and reset DNF module streams on Rocky Linux to get exact versions like Node.js 14, with steps, trade‑offs, and a reset procedure.
Goal Determine whether a module stream enabled on Rocky Linux 8 remains active after upgrading to Rocky Linux 9. Constraints and Uncertainty The dnf module system records enabled streams and preserves them across minor releases, but the official documentation does not specify how stream state is handled during a major distribution upgrade. Reproducible build
Transition to NetworkManager Rocky Linux 9 removes legacy network-scripts by default, shifting primary interface management to NetworkManager. In previous versions, manual edits to files in /etc/sysconfig/network-scripts/ were often sufficient to define static IP configurations that persisted across reboots via the network service. Configuration Sync Uncerta
PostgreSQL service on Rocky Linux: configuring StopWhenUnneeded to control idle connections The goal is to ensure that idle PostgreSQL connections are released when the systemd service is stopped or restarted, thereby reducing the risk of connection pool exhaustion under variable workloads. Currently the default max_connections is 100, idle_in_transaction_se
DNSSEC validation failed in Rocky Linux 9 The goal is to enable DNSSEC validation for applications that demand it. In Rocky Linux 9, systemd-resolved disables DNSSEC by default, leading to errors such as DNSSEC validation failed or DNSSEC not enabled . This default setting impacts services that rely on strict DNSSEC enforcement, including some browsers and c
Systemd socket activation is frequently discussed as a path to zero-downtime application upgrades on Rocky Linux because the listening socket can stay open while the service binary is replaced. The documented requirement is that the application must accept the file descriptor from systemd rather than binding the port itself. For legacy binaries that do not s
Rocky Linux uses DNF to manage packages, and its download layer retries transient network failures according to configured retry, timeout, and minrate values. Completed payloads are written to temporary files and renamed into place, which prevents duplicated or truncated package files on a re-attempted download. The unresolved boundary sits at the RPM transa
Goal Determine whether per-service systemd resource ceilings — LimitNOFILE (file descriptors) or TasksMax (threads/processes) — are the first bottleneck hit when a connection pool exhausts on Rocky Linux 8 or 9. Constraints and uncertainty Rocky 9 defaults to cgroup v2 while Rocky 8 uses hybrid or v1 unless configured, changing how limits are enforced and ob
Rocky Linux offers two documented accessibility paths in its Anaconda installer, and a deployment plan for blind and low-vision users has to commit to one before the capabilities of every target machine are known. The goal is to standardize a single installation procedure that stays dependable across mixed hardware. The text-mode console can be made accessib