-
Notifications
You must be signed in to change notification settings - Fork 3
Docker
FolderView Plus enhances the Unraid Docker page without replacing container configuration or application data. Saved folders organize native rows and expose eligible actions through folder-aware controls.
| View | Purpose |
|---|---|
| FolderView | Groups native container rows into the saved hierarchy. |
| Host list | Restores the normal Unraid Docker table without FolderView grouping. |
| Command | Presents a folder-oriented command surface while retaining native container actions. |
Changing views does not delete folder configuration. Reset view clears temporary toolbar filters and returns to the normal unfiltered state.
Screenshot placeholder — Docker view menu
Capture the View menu with FolderView, Host list, and Command choices. Use test container names and enable Privacy before capture.
FolderView leaves native rows available during startup, obtains a coherent inventory snapshot, and then groups visible rows. Later start/stop/update changes reconcile incrementally when structural configuration has not changed.
- Expand a folder to show native container rows.
- Collapse it to show the configured preview.
- Direct members and child folders remain distinct.
- Host list is the fastest comparison when investigating grouping behavior.
On a compatible Unraid host, FolderView Plus prefers the local Unraid GraphQL API for Docker runtime-state reads. This requires no FolderView Plus setting, API key, remote connection, or GitHub secret. Capability detection happens locally each time the runtime is prepared.
The ownership boundary is intentionally conservative:
- Native Unraid/PHP inventory remains authoritative for which rows exist and for configuration metadata.
- GraphQL enriches those known rows with current state by matching stable container name and ID evidence.
- A lifecycle action first requests the affected container when the host supports targeted reads; periodic refresh uses the supported full-container query.
- Native Unraid controls remain the action owner on the legacy Docker page. API availability does not replace host menus or create duplicate container rows.
When the endpoint, permission, query shape, or requested capability is unavailable, FolderView Plus automatically uses its established PHP snapshot path. Temporary rate limits and service failures use bounded cooldowns before another API attempt. Existing folders and native rows stay usable during fallback.
Diagnostics expose only an aggregate provider state such as ready, fallback, cooldown, or unavailable. They do not export GraphQL results, container identities, query text, tokens, cookies, or server error details.
Eligible folder actions may start, stop, pause, resume, restart, or update members. Eligibility is calculated from current state and supported host actions; unsupported operations are hidden or disabled. Folder locks prevent accidental branch-level operations.
Always review the selected scope. A folder action may operate on several containers.
Collapsed preview cards can expose quick icons for Open WebUI, View logs, and Open Console when the container and host support them. These controls act on the selected member, not the complete folder.
The responsive Action Bar provides:
- Add Folder, Expand All, and Collapse All.
- Temporary Unassigned, Updates, Empty, and Health Issues filters with live counts.
- Manage Folders and the View menu.
- Show/hide empty folders, clear folder focus, refresh folder state, Bulk Assignment, Rules, Reset view, and Capture page diagnostics under Tools.
Unassigned/update/health filters are temporary and do not rewrite saved folder order or visibility. Show/Hide empty folders changes the persisted hideEmptyFolders preference. Reset view clears the temporary filter/focus state and returns all eligible rows.
Screenshot placeholder — Docker Action Bar
Capture live filter counts plus View and Tools menus using fictional containers and Privacy.
Command View is a FolderView-owned operational surface. Each folder card summarizes direct/descendant counts and eligible states, then offers branch-aware commands:
- Start branch and Stop branch.
- Update branch when updates are known.
- Force update when no normal update branch is available; use only when you intentionally want Unraid's force-update behavior for the branch.
- Open WebUIs for eligible members.
- Edit the folder.
Branch commands include descendants. Review displayed eligible counts before continuing; locked or ineligible members remain excluded or disabled.
Screenshot placeholder — Docker Command View
Capture one branch card with state counts and the five command buttons. Use disposable test containers.
Folder summaries can show running/stopped/update badges, state details, trends, attention accents, and a runtime health badge. Docker health presets control how stopped percentages, updates, and all-stopped conditions affect severity. These are presentation and operator-awareness tools; they do not change container state.
The Docker-page Privacy control can mask names/icons, LAN IPs, ports, volume paths, registries, public IPs, interfaces, and external URLs. It changes rendered text, copied text, labels, tooltips, links, and new rows observed while enabled. It does not modify Docker configuration. See Privacy.
Compose Manager is an optional integration. FolderView Plus detects compatible labels and metadata where supported, but behavior depends on installed versions and available host markup. If rows are missing or duplicated, compare Host list, disable conflicting custom overrides, and include plugin versions in the report.
When FolderView Plus detects an unsupported or future native Docker surface, it preserves Unraid's page and avoids injecting a second folder hierarchy. A safe-mode banner is a compatibility protection, not proof that saved folder data was deleted.
Do not force legacy selectors onto a native page. Capture diagnostics and check Compatibility and Performance.
- Switch to Host list and confirm native rows exist.
- Reset temporary view filters.
- Expand the affected folder and compare direct members.
- Hard-refresh after plugin updates.
- Disable custom CSS/JS temporarily.
- Use Tools -> Capture page diagnostics before leaving the affected layout.
- Copy runtime-banner diagnostics before refreshing if an error is present.
- Run Settings Diagnostics, confirm the capture is fresh, and attach a sanitized bundle.
An API fallback by itself is not data loss and normally requires no action. If runtime state appears stale, capture diagnostics before refreshing and include the aggregate API provider state in the report.
See also: Docker Start Order · Folder Management
FolderView Plus Wiki · Stable releases · Report an issue · Unraid forum · Security reporting