Please confirm these before moving forward.
Describe the new feature
It would be useful if UniGetUI could manage updates for local Docker Compose stacks.
The basic idea would be to treat each Compose project as one package. UniGetUI could scan one or more configured directories for:
compose.yaml
compose.yml
docker-compose.yml
For example:
C:\docker\n8n
C:\docker\speakr
Each stack could then appear under Software Updates, for example:
n8n Update available - 1 image
Speakr Update available - 2 images
Updating a stack could essentially run:
docker compose pull
docker compose up -d
from that project's directory.
One important detail is update detection. Many Docker images use tags such as latest, so comparing version/tag strings is not enough. Ideally, UniGetUI would compare the local image digest with the current remote digest.
A minimal initial implementation could support:
- Configurable Compose stack directories
- Automatic stack discovery
- Detection of updated images
- Updating the whole stack
- Showing Docker Compose output/errors
- Ignoring or marking services that only use
build:
I would avoid stack deletion, volume deletion, or similar destructive operations initially.
If it fits UniGetUI's package-manager architecture, Docker Compose could potentially be implemented as another manager, with each Compose project representing one installed package.
Using the existing Docker CLI would also mean Docker Desktop credentials and private registry authentication should continue working normally.
The goal would be to let UniGetUI act as a single update dashboard for both normal Windows applications and locally hosted Docker services.
Describe how this new feature could help users
Unified updates as the project suggests :)
Please confirm these before moving forward.
Describe the new feature
It would be useful if UniGetUI could manage updates for local Docker Compose stacks.
The basic idea would be to treat each Compose project as one package. UniGetUI could scan one or more configured directories for:
For example:
Each stack could then appear under Software Updates, for example:
Updating a stack could essentially run:
from that project's directory.
One important detail is update detection. Many Docker images use tags such as
latest, so comparing version/tag strings is not enough. Ideally, UniGetUI would compare the local image digest with the current remote digest.A minimal initial implementation could support:
build:I would avoid stack deletion, volume deletion, or similar destructive operations initially.
If it fits UniGetUI's package-manager architecture, Docker Compose could potentially be implemented as another manager, with each Compose project representing one installed package.
Using the existing Docker CLI would also mean Docker Desktop credentials and private registry authentication should continue working normally.
The goal would be to let UniGetUI act as a single update dashboard for both normal Windows applications and locally hosted Docker services.
Describe how this new feature could help users
Unified updates as the project suggests :)