Repository navigation
Search containers and group them by Compose project or Docker folder #318
Description
What and why
Let users search the container list and group containers by Compose project or by the Docker folders of the Unraid webGUI.
User demand: "Collapsible groups for Docker containers by Compose stack ... the one thing holding me back" (r/unRAID, 2026-05-27, in the thread https://www.reddit.com/r/unRAID/comments/1to74ec/ ; second-hand from a research lane, medium confidence).
Other apps: U-Manager lists "filter and search" for Docker (https://play.google.com/store/apps/details?id=es.atrapandocucarachas.umanager).
What NOVA has today
ui/screens/docker/DockerTab.kt groups by state only (Running / not running, DockerTab.kt:146-159). There is no search field. GetDockerContainers (queries.graphql:79) does not request labels or the organizer.
API side
The upstream schema has DockerContainer.labels and docker.organizer. The minimum API version for these fields was not checked; the Compose project is normally the label com.docker.compose.project, which is not verified against a server.
Constraints from NOVA's principles
Official API only. New fields must not break servers at the 4.30.0 floor (capability detection, see #247).
Open questions
- Compose project, webGUI folders, or both?
- Is the folder structure readable with a least-privilege key?
Acceptance criteria
- A search field filters the container list by name and image.
- Containers can be grouped by Compose project (and/or webGUI folder) with collapsible groups.
- Older servers keep the current layout.
Size
M
Activity
nofuturekid commentedon Nov 13, 2026
PR #335 builds search (clear button, empty state, text kept across tab switches and rotation) and grouping by Compose project (the
com.docker.compose.projectlabel;DockerContainer.labelsexists in the upstream schema since API 4.29, same read permission as the container list).Follow-up, not built here: grouping by the web interface's own Docker folders (the
docker.organizerAPI). Its minimum API version is not verified, and whether a least-privilege key can read it is open. It should wait for the capability detection / capability model so older servers keep the current layout. Collapsible groups are also not part of this PR, because the existing Grouped layout is not collapsible either.