Linux OverlayFSCopy Anchor Link

Riftri supports OverlayFS on Linux when the caller's mount namespace passes the active probe, directly or through the optional mount helper. Without native reflinks, OverlayFS shares a read-only base while each worktree stores its changes in a private layer.

View .md / Copy .md

Check supportCopy Anchor Link

riftri doctor --destination ../app-auth

Riftri prefers reflinks and selects OverlayFS only if it can create a usable mount. Containers and restricted shells may not allow it.

Optional mount helperCopy Anchor Link

If the diagnostic calls for it, an administrator installs the helper once:

sudo riftri overlayfs install-helper

The helper is privileged and system-wide — review View .md before installing. It only performs validated mount operations; repository enablement stays separate. Then create worktrees normally:

riftri worktree add ../app-auth -b feature/auth main

After a rebootCopy Anchor Link

Mounts disappear; stored private changes remain. From the repository, keeping any custom --state-dir argument:

riftri repair

Repair restores the mount without rebuilding private changes and stops if the path or mount identity is ambiguous.

Mounted moves and compaction are unsupported. Remove managed worktrees with Riftri; never delete their backing layers manually.

Edit on GitHub