Unraid announced version 8 on August 17, and it is the largest change the NAS platform has made since V6: the Slackware base it has used for roughly two decades is being replaced with Universal Blue’s uCore, an immutable OCI-based server image built on Fedora CoreOS.

Why leave Slackware

Slackware served Unraid well for a long time, and the reason to leave is not that it stopped working.

It is that Slackware’s release cadence and package availability were never designed for a product that needs to ship security updates quickly across a large, standardized base. Unraid’s developers cite exactly that: faster security updates and a larger, more standardized Linux foundation.

Anyone who has tried to install something on Unraid that was not in Community Apps understands the practical version of this problem. You end up hunting Slackware packages, using Nerd Tools, or giving up and running it in a container.

What uCore brings

uCore is part of the Universal Blue project, the same lineage as Bazzite on the desktop side. The model is an immutable OCI image: the operating system is a container image you boot, updates are atomic, and rollback is a matter of booting the previous image.

For a NAS this is a strong fit. The base OS on a storage appliance should be boring and replaceable, and the interesting state lives on the array and in your containers rather than in the root filesystem.

Three other changes come with it:

Selectable kernels. Users on new hardware can choose a newer kernel, while anyone who does not need the latest support can stay on a long-term version. That has been a recurring pain point, since a NAS running old hardware and a NAS running a brand new HBA want very different kernels.

Built-in backups. Unraid 8 includes a backup solution that targets cloud storage, S3-compatible services, or another Unraid server, with snapshots and full restores built into the product rather than assembled from plugins.

Docker Compose in Community Apps. Compose has been available through community plugins for a while; version 8 builds it in directly.

That last one is overdue. Most self-hosted software is distributed as a Compose file, and the gap between “here is the official docker-compose.yml” and Unraid’s template system has been a persistent source of friction. Our Docker Compose basics guide covers the format that is now first-class here.

Worth watching, not worth panicking about

This is an announcement rather than a release. There is no shipping build to install yet, and a base-OS change of this size on a platform where people store irreplaceable data deserves a cautious upgrade path.

The concerns are the predictable ones: plugins that assumed a Slackware userspace, custom scripts in /boot/config/go, and anything that installed packages outside the supported mechanisms. An immutable base is more robust precisely because it stops you doing those things, which means some existing setups will need rework.

Still, the direction is right. Unraid has been the odd one out among NAS platforms for years, running a general-purpose distribution from 1993 under a product that competes with appliance operating systems. Moving to an immutable image with atomic updates puts it in the same category as TrueNAS Scale and gives it a security update story it did not previously have.