Unraid 8 drops Slackware after two decades to build on uCore, an immutable Fedora base
Unraid announced that its next major release will replace Slackware, its foundation for roughly twenty years, with Universal Blue’s uCore, an immutable OCI server image built on Fedora CoreOS. Built-in backups, native Docker Compose, and plugin permissions arrive with the architectural shift.
August 21, 2026. Unraid announces the next major version of its NAS-focused operating system. August 2026. The project formalizes a move to Universal Blue’s uCore, an immutable OCI server image built on Fedora CoreOS. Twenty years. That is roughly how long Slackware has served as the product’s foundation.
It is the biggest change in the platform’s history. Unraid 8 abandons the Slackware base it has carried for two decades in favor of Fedora, with a stated goal: faster security updates and a larger, more standardized Linux base.
Why leave Slackware now
Slackware was a defensible choice for years: stable, predictable, slow to change. But that slowness has a cost. The security-update cadence depends on a smaller community, and the deliberately conservative base forces Unraid to maintain part of the integration that other distributions ship out of the box.
Fedora, by contrast, tracks the kernel and the modern Linux ecosystem closely. The project justifies the move with two concrete benefits: faster security updates and a more standardized base to build on. For a product sold as a NAS you install and forget, receiving patches without friction is a substance argument, not marketing.
The bet is all the more coherent because Unraid’s mental model was never that of a classic distribution. The product has always treated the underlying OS as a state you can reset by rebooting, rather than a permanent accumulation of changes. That is exactly the philosophy of an immutable system — so the match is no accident.
uCore: an immutable OCI base
uCore is Universal Blue’s server image, built on Fedora CoreOS and distributed as an OCI image. It is a lightweight, immutable base that already ships many of the tools and services commonly used on a server. The appeal for Unraid is twofold: a cleaner separation between the base system and the Unraid software on top, and reuse of the existing image streams — stable, testing, and long-term support.
That separation changes day-to-day maintenance. The base system becomes a versioned artifact you replace, not a directory you patch by hand. For a NAS holding a household’s or small business’s data, that is the difference between an OS you update with confidence and one you dread touching.
Kernel flexibility follows. Unraid plans to let users on new hardware pick a newer kernel, while those who do not need the latest features stay on a stable long-term version. uCore’s streams make that choice structural rather than improvised.
Backups, Compose, and plugin permissions
Beyond the base, Unraid 8 announces three additions that touch everyday self-hosting.
Built-in backups. Users will be able to back up to cloud storage, an S3-compatible service, or another Unraid server, with snapshots and full restores built into the product. It is a long-standing gap in consumer NAS platforms that Unraid chooses to close natively rather than through a plugin.
Native Docker Compose. Today, Compose relies on community plugins. Version 8 builds it into Community Apps: Compose-defined applications will appear alongside regular apps, with no separate interface. For anyone already managing services as compose.yml files, that removes a needless point of friction.
A plugin permission system. Before install, Unraid 8 will show what a plugin can access and let the user decide whether those permissions are acceptable, backed by a new SDK. On a platform where plugins have long had broad system access, it is a welcome security guardrail.
What does not change
Unraid is explicit on one point: the advanced features stay. VLANs, NIC bridging, and other networking options for experienced users do not disappear. Moving to Fedora and an immutable base does not mean sanding the product down — the promise is to keep the depth while changing the foundations.
The timeline, for its part, is deliberately vague. Everything is still in development, reachable through a beta waitlist, and will pass through several testing stages before general availability. Unraid commits to no date — a sensible caution for a migration of this scale.
What it changes in the NAS ecosystem
Unraid’s choice lights up a wider movement. TrueNAS Scale already bet on Debian over FreeBSD, and Synology keeps its own proprietary base. Moving to Fedora CoreOS puts Unraid in the camp of immutable systems gaining ground on home servers — the same model powering Fedora CoreOS, openSUSE MicroOS, and the Universal Blue desktop images.
For the end user, the difference comes down to one word: predictability. An immutable base updates by replacing an image, not by accumulating packages. The risk of drift — a system modified once, then twice, until it no longer resembles anything reproducible — disappears by construction. For a NAS meant to stay in service for years, that is a substance argument, not a cosmetic detail.
The trade-off is a learning curve. Slackware veterans used to tinkering directly in /etc will have to go through the intended mechanisms: systemd, versioned configuration files, containers. Unraid knows this and promises to keep the advanced features; but the ergonomics of troubleshooting change, and that is an adjustment not to underestimate at migration time.
Before migrating, three checks are in order:
- Inventory your plugins and verify compatibility with the new SDK: the permission system will likely break those that have not been ported.
- Test your restores: Unraid 8’s native backup does not replace an existing strategy, it complements it — validate a full restore before switching.
- Standardize your Compose stack: moving to native Compose in Community Apps is the moment to consolidate your
compose.ymlfiles rather than leaving them scattered across plugins.
Data sovereignty is the quieter argument underneath the backup feature. A NAS exists to hold data you do not want in someone else’s cloud; a native backup that can target another Unraid server, an S3 bucket you control, or a cloud of your choosing keeps that sovereignty intact end to end. The old model — a plugin, a cron job, a vague hope that the restore actually works — quietly undermined the whole point of self-hosting. A first-party, tested restore path closes the loop, and an immutable base makes those restores more trustworthy: a system brought back to a known image is a system you can reason about.
Verdict
If you run Unraid in production today, change nothing: the current version remains supported and version 8 is not ready. But join the beta if your workload allows, and start cataloguing the plugins you depend on — the new permission system and the base migration will break some of them until they are ported to the new SDK.
If you are still weighing Unraid against an alternative, this shift settles an old debate. Those who faulted Unraid for its aging Slackware base will see confirmation of a product modernizing its foundations; those who prized Slackware’s quiet stability must recognize that the new base, immutable and current, delivers the same reliability contract by a different route.
Migrating an OS base after twenty years is never routine. But by pairing it with native backups, built-in Compose, and plugin permissions, Unraid turns a technical overhaul into a user-facing redesign.