iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Keep a Rocky Linux 8 server on the supported 8.10 minor release and apply updates with sudo dnf upgrade. Before changing packages, confirm the installed release and repositories, review advisories with dnf updateinfo, arrange an appropriate maintenance window, and make sure you have console or out-of-band access. Rocky Linux 8 active support ended on 2024-05-31, but security support is listed through 2029-05-31, so timely patching remains important.
What supported means for Rocky Linux 8
Rocky Linux’s current release table lists Rocky Linux 8, codename Green Obsidian, with a release date of 2021-05-01 and 8.10 as the latest and current minor release. Rocky supports only the latest minor release within a major version. A server left on 8.9 or an earlier 8.x release is therefore not in the supported update state, even though its major-version label still says Rocky Linux 8.
Recommended Free Tools
| Lifecycle item | Rocky Linux 8 status | What an administrator should do |
|---|---|---|
| Latest minor release | 8.10 | Use supported Rocky repositories and run the normal DNF upgrade. |
| Active support ended | 2024-05-31 | Do not expect the active-support feature and maintenance phase to continue. |
| Security-support end date | 2029-05-31 | Continue applying available security updates until that listed date, subject to Rocky’s published policy. |
| Older minor releases | Superseded content moves to the vault | Upgrade to the latest supported minor release rather than relying on vault content for current fixes. |
Rocky describes its ten-year lifecycle as five years of active support followed by five years of security support. Its lifecycle documentation also gives a normal update-delivery target of 24–48 hours after an upstream release when packaging work is routine, no new upstream dependencies are introduced, and the development team can complete the work. That is a target, not a guarantee for every package or security incident.
Rocky’s lifecycle guidance says the previous minor version receives neither bug-fix nor security updates after it is superseded. A repository that still contains old packages is not evidence that the old minor release is supported.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Before you update: establish the starting state
Record the release, enabled repositories, and currently published advisories before modifying packages. This gives you a change record and helps distinguish a repository problem from a package or service problem.
cat /etc/rocky-release
sudo dnf repolist
sudo dnf updateinfo summary- Release file: confirms the installed Rocky Linux release and minor version.
- Repository list: shows where DNF will obtain packages. Check that the enabled repositories are intentional for this server and environment.
- Advisory summary: provides Rocky’s documented interface for reviewing available security, bug-fix, and enhancement advisories.
Also identify the services that must remain available, the person who can approve a reboot, and a recovery path if the transaction or reboot does not complete normally. A kernel, glibc, systemd, or other core-package update can require a restart, and the impact depends on the host’s workload. Rocky’s documentation does not prescribe one universal maintenance window or reboot rule for every transaction.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Review advisories and plan the maintenance window
Use dnf updateinfo before the upgrade to understand which security, bug-fix, and enhancement advisories are available. The advisory review should be part of change planning rather than an after-the-fact check.
- Confirm the host identity, installed Rocky release, and enabled repositories.
- Review the available advisory categories with
sudo dnf updateinfo summaryand the broaderdnf updateinfointerface as needed. - Check application owners for compatibility concerns, especially where the server uses modular application streams.
- Schedule a window appropriate to the services on the host. Include time for package download, installation, possible reboot, and post-update validation.
- Ensure console or out-of-band access is available before updating the kernel or core libraries. SSH alone may not be sufficient if the network stack or boot process fails.
- Keep a copy of the planned command, advisory list, transaction output, and validation results with the change record.
Run the normal Rocky Linux 8 update
The routine maintenance command is:
sudo dnf upgradeReview the proposed transaction, dependencies, removals, and disk-space requirements. Confirm only after the package set matches the change you approved.
For a noninteractive transaction that has already been reviewed and authorized, Rocky’s 8.10 release notes show:
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
sudo dnf -y upgradeWith supported repositories configured, the documented result is an upgrade from a Rocky Linux 8.x installation to 8.10. The -y option accepts DNF’s prompts automatically; it does not replace the need to inspect the transaction before running it in production.
Free tools Windows power users keep installed
One-click scans. No signup required.
What the command changes
DNF resolves newer versions of installed packages and their dependencies from the enabled repositories. It may update the kernel, libraries, system services, language runtimes, and applications. The exact package set varies by the advisories available, enabled repositories, installed software, and dependency constraints on that host.
What not to assume
- A successful package transaction does not prove that every service restarted correctly.
- Installation of a new kernel does not by itself prove that the server is running it.
- Being on major version 8 does not prove that the host is on supported minor version 8.10.
- An advisory summary does not substitute for checking application compatibility and service health.
Decide whether a reboot is required
After DNF finishes, determine whether the updated packages require a reboot. A restart is commonly relevant when the transaction replaces the running kernel, glibc, systemd, or another core component, but there is no single Rocky-published command or guaranteed reboot requirement for every update transaction.
- Inspect the transaction output and identify whether the kernel or other core components changed.
- Use the approved maintenance window if a reboot is needed.
- Reboot through your normal operational process, with console or out-of-band access available.
- After the host returns, verify the running kernel, release, repositories, and critical services.
Do not schedule a reboot solely because an update was available, and do not skip one when your operational checks show that the running system still uses replaced core components. The decision must account for the packages changed and the workload hosted on the server.
Validate the server after updating
Post-update validation should demonstrate both that the operating system changed as intended and that the applications which depend on it are healthy.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
cat /etc/rocky-release
uname -r
sudo dnf repolist
sudo systemctl --failed- Confirm that
/etc/rocky-releasereports the expected Rocky Linux 8.10 state. - Check
uname -rafter a reboot to verify which kernel is actually running. - Recheck enabled repositories and investigate any repository that disappeared, was disabled, or is no longer approved.
- Review failed units and then perform application-specific health checks, such as a local endpoint test, database connection test, queue check, or service status check.
- Compare monitoring data before and after the maintenance window for error rates, latency, disk usage, and resource saturation.
- Save the DNF transaction output and advisory results so the change can be audited or rolled back operationally if necessary.
Check application streams after the OS update
Rocky Linux 8.10 release notes specifically call attention to application streams that are end-of-life or deprecated. An operating-system upgrade can leave an application stream in a state that is no longer maintained or no longer the preferred stream for that software.
- List the enabled module or application streams using the module-management tools already used in your Rocky Linux 8 environment.
- Identify streams marked EOL or deprecated in the 8.10 release information.
- Ask the application owner whether the service can move to a newer supported stream.
- Test the newer stream in a staging environment when the application is business-critical or has a strict compatibility requirement.
- Update the stream and its configuration during an approved window, then validate the service, data access, extensions, and client compatibility.
Do not switch streams blindly during a security patch window. The operating-system update and an application-stream migration may have different testing, backup, and rollback requirements.
If the server is on Rocky Linux 8.9 or earlier
Do not treat an older 8.x minor release as supportable simply because it is still in the Rocky Linux 8 family. Rocky states that only the latest minor release is supported. When a newer minor release supersedes an older one, the older content moves to the vault and stops receiving bug-fix and security updates.
First confirm the installed release and repository configuration:
cat /etc/rocky-release
sudo dnf repolistThen correct the repository configuration so DNF can reach supported Rocky Linux 8 content and run:
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
sudo dnf upgradeAfter the transaction, verify that the host reports 8.10 and repeat the application-stream and service-health checks. If the system cannot reach supported repositories, diagnose that repository configuration or network issue rather than assuming vault content is current. A vault is historical package storage, not a source of ongoing security maintenance.
Emergency path for an actively exploited vulnerability
Rocky documents an optional security repository for a narrow emergency case: a critical vulnerability is actively exploited, public proof of concept is circulating, and waiting for the upstream Enterprise Linux release would leave administrators exposed.
sudo dnf --enablerepo=security updateThis is not a second normal release channel. Rocky describes packages in this repository as versioned so that official upstream releases will supersede them; it is a hotfix mechanism, not a parallel release track.
Use the security repository as an exception
- Confirm that the vulnerability meets the emergency criteria rather than merely being high priority in an advisory list.
- Record the affected service, exposure, advisory or incident reference, approver, and reason ordinary repositories cannot be used in time.
- Ensure console or out-of-band access and a tested recovery plan are available.
- Run
sudo dnf --enablerepo=security updateduring an approved emergency window. - Validate the affected service, host behavior, and monitoring signals immediately afterward.
- When the official upstream update becomes available, run the ordinary repository update so the official package supersedes the hotfix.
- Document the reconciliation and remove any temporary repository enablement or exception that is no longer needed.
Do not use this repository as a routine way to obtain faster updates, and do not leave a temporary emergency process undocumented. The ordinary Rocky repositories remain the normal source for scheduled maintenance.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choosing an update strategy
Most servers should use routine updates with advisory review and staged validation. An emergency hotfix is justified only by the conditions Rocky describes. The following comparison keeps the decision tied to package source, trigger, support state, risk, and application compatibility.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
| Strategy | Package source | Trigger | Operational risk | Application-stream handling |
|---|---|---|---|---|
| Routine maintenance | Normal Rocky repositories | Scheduled maintenance and advisory review | Standard DNF transaction, reboot decision, and service validation | Review EOL or deprecated streams after the OS update and plan migrations separately when needed |
| Staged update | Normal Rocky repositories, first in a representative test or canary group | Need to reduce blast radius for a fleet or sensitive service | Requires extra coordination and time, but exposes compatibility issues before broad rollout | Test stream changes with the application before production rollout |
| Emergency hotfix | Optional Rocky security repository, enabled for the transaction | Actively exploited critical vulnerability with public proof of concept and unacceptable exposure while waiting for upstream | Exceptional package path that must later be reconciled with the official upstream release | Validate the affected application immediately and return to normal repositories when the upstream package is available |
| Leaving an old minor release in place | Vault or stale repository content | No valid maintenance trigger | Unsupported state with no continuing bug-fix or security updates | Application compatibility cannot compensate for an unsupported operating-system minor release |
Troubleshoot common update problems
DNF cannot find current Rocky packages
Start with the recorded release and repository list. Check whether the host is still pointed at repositories for a superseded minor release, whether a repository is disabled, and whether DNS, proxy, firewall, or certificate problems prevent access. Do not “fix” the issue by treating vault content as current security content. Correct the repository configuration, rerun the advisory check, and then perform the normal upgrade.
The transaction proposes unexpected removals or dependency changes
Stop and review the proposed transaction instead of accepting it automatically. Identify which enabled repository or application stream introduces the dependency change, confirm the package ownership with the service owner, and test the change where possible. Use sudo dnf -y upgrade only after the transaction has already been reviewed and approved.
The update completed but a service failed
Check the failed unit, its journal, configuration changes, dependency versions, and application logs. Verify that the service account can access its files, ports, certificates, and databases. If the failure is caused by an application-stream change, restore the last known-good application configuration according to the service’s recovery plan and schedule a properly tested stream migration.
The host does not boot after a kernel update
Use console or out-of-band access to inspect the boot menu and system logs. Preserve the failed boot information, select a previously working kernel only under your organization’s recovery procedure, and open a change or incident record. Once service is restored, investigate the kernel transaction, storage, bootloader, drivers, and third-party modules before attempting another reboot.
A security issue is urgent but the ordinary update is not available
Determine whether the situation matches Rocky’s documented actively exploited vulnerability criteria. If it does, use the optional security repository command as an exception, record the decision, validate the host, and reconcile the package with the official upstream release later. If it does not, use the normal advisory and maintenance process rather than treating every urgent ticket as a hotfix case.
Operating Rocky Linux 8 through its remaining lifecycle
Because active support ended in 2024 while listed security support runs through 2029-05-31, organizations should distinguish security maintenance from planning for a future platform transition. Keep 8.10 patched while it remains an approved platform, inventory workloads and application streams, and establish a migration plan before the security-support end date.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallIf an organization cannot yet install a supported new system and migrate its data, Rocky’s lifecycle guidance says it may seek a support provider. Such providers maintain their own packages and policies outside the Rocky Linux ecosystem, so evaluate their support boundary, package provenance, response commitments, and migration responsibilities separately from Rocky’s own release policy.
A repeatable maintenance checklist
- Record
cat /etc/rocky-releaseoutput. - Record
sudo dnf repolistoutput and confirm repository ownership. - Review advisories with
sudo dnf updateinfo summaryand the broaderdnf updateinfointerface. - Confirm backups, recovery procedures, service owners, and console or out-of-band access.
- Schedule a window that allows package installation, reboot if required, and validation.
- Run
sudo dnf upgrade; usesudo dnf -y upgradeonly after review and approval. - Determine whether the changed kernel or core libraries require a reboot.
- Verify release, running kernel, repositories, failed units, and critical applications.
- Review EOL or deprecated application streams and plan supported replacements.
- Use
sudo dnf --enablerepo=security updateonly for Rocky’s documented actively exploited vulnerability scenario. - Store transaction output, advisory results, approvals, and post-update checks with the change record.
Bottom line
For normal Rocky Linux 8 maintenance, verify the host and repositories, review advisories, and run sudo dnf upgrade to reach the supported 8.10 minor release. Reboot only when the changed packages and workload require it, then verify the running kernel and application health. Treat EOL application streams, superseded minor releases, and emergency security-repository updates as separate operational decisions, and keep a migration plan for the end of Rocky Linux 8 security support on 2029-05-31.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
