The openSUSE project has moved Leap 16.1 into its Release Candidate phase, and the headline addition is a new option at install time: a transactionally updated system with a read-only root filesystem.
RC Images Now Available
Release Candidate images are published at get.opensuse.org. The project notes that the RC stage is typically when users begin serious testing, making this the right moment to download an image and evaluate the release.
When booting the installer, users will now find the option to configure the system as immutable. The alternative — a conventional mutable installation familiar from previous Leap releases — remains fully available. Neither path is required; the choice belongs to the installer at setup time.
What the Immutable Option Provides
Under the immutable model, the base operating system sits behind a read-only root filesystem. Updates arrive as complete transactions rather than piecemeal changes, and the system can roll back to a previous working state if an update introduces a problem.
The openSUSE announcement positions this alongside tools already popular in container-oriented workflows. The immutable base pairs with application-level tools such as podman, distrobox, and Flatpak, which let users run software in isolated environments while the underlying system remains fixed. Teams building on container-native practices may find this separation of system and application management a natural fit.
An Option, Not a Migration
What distinguishes Leap 16.1 from dedicated immutable distributions is that the feature is opt-in. Administrators who have standardized on traditional Leap package management see no change to their workflow unless they choose otherwise. Those curious about the immutable approach can test it on a single machine without rearchitecting existing infrastructure.
This lowers the barrier to evaluation significantly. Rather than choosing between two separate distributions, teams running Leap can explore the immutable model within a familiar release cycle and ecosystem.
Community Testing Invited
The RC phase is where the project invites real-world feedback. openSUSE is encouraging users to report bugs, test upgrade paths from earlier Leap versions, and confirm hardware compatibility. The stability of the eventual release depends heavily on the volume and quality of testing during this window.
For organisations evaluating long-term Linux strategies, Leap 16.1 RC offers a chance to assess an immutable approach on an enterprise-grade distribution while the traditional option remains one click away.
openSUSE 項目已將 Leap 16.1 推進至候選版本階段，其重點新增功能是在安裝時提供一個新選項：一個具有只讀根檔案系統的交易式更新系統。
候選版本映像現已可用
候選版本映像已發佈於 get.opensuse.org。項目指出，候選版本階段通常是用戶開始認真測試的時機，因此現在是下載映像並評估此版本的合適時刻。
啟動安裝程式時，用戶現在會發現一個選項，可將系統配置為不可變模式。另一個選項——即從前幾個 Leap 版本沿用下來的傳統可變安裝——仍然完全可用。兩種路徑均非強制；選擇權在安裝時由用戶決定。
不可變選項提供的功能
在不可變模型下，基礎作業系統位於一個只讀根檔案系統之後。更新以完整交易的形式送達，而非零散的變更，如果更新引入問題，系統可以回滾到先前的正常工作狀態。
openSUSE 的公告將此定位為與現已流行於容器導向工作流程的工具並列。不可變基礎系統與 podman、distrobox 和 Flatpak 等應用程式層級工具結合使用，這些工具讓用戶在隔離的環境中運行軟體，同時底層系統保持不變。基於原生容器實踐建立的團隊可能會發現，這種系統與應用程式管理的分離十分自然契合。
一個選項，而非一次遷移
使 Leap 16.1 與專用的不可變發行版有所區別的是，此功能是可選的。已將工作流程標準化在傳統 Leap 套件管理的管理員，除非他們另有選擇，否則其工作流程不會有任何改變。那些對不可變方法感興趣的人，可以在不重新規劃現有基礎設施的情況下，在單台機器上進行測試。
這顯著降低了評估的門檻。運行 Leap 的團隊無需在兩個獨立的發行版之間做出選擇，而是在一個熟悉的版本週期和生態系統內探索不可變模型。
邀請社群測試
候選版本階段是項目邀請真實反饋的時機。openSUSE 鼓勵用戶報告錯誤、測試從早期 Leap 版本升級的路徑，並確認硬件兼容性。最終版本的穩定性在很大程度上取決於此期間測試的數量與質量。
對於評估長期 Linux 策略的組織而言，Leap 16.1 RC 提供了一個機會，在一個企業級發行版上評估不可變方法，同時傳統選項仍觸手可及。