lazydocker icon indicating copy to clipboard operation
lazydocker copied to clipboard

Feature request: Manage Docker Compose stacks (up/down)

Open davipro34 opened this issue 4 months ago • 3 comments

Is your feature request related to a problem? Please describe.
Currently, Lazydocker allows managing containers, images, and volumes individually, but it does not provide a way to control Docker Compose stacks as a whole.
This makes it cumbersome when working with multi-container applications, since users need to leave Lazydocker and manually run docker compose up -d or docker compose down from the CLI.

Describe the solution you'd like
I would love to see Lazydocker support basic stack management.
For example:

  • Detect docker-compose.yml files in a configured directory.
  • Allow starting/stopping/restarting a full stack (equivalent to docker compose up -d / docker compose down).
  • Possibly provide a simple "Stacks" view, similar to how containers are currently listed.

Describe alternatives you've considered

  • Using Lazydocker only for container-level management and relying on CLI commands for stacks.
  • External TUI scripts with fzf or other tools to wrap docker compose commands.
  • Using Portainer (works well for stacks, but is a web UI, not a TUI like Lazydocker).

Additional context
This feature would greatly improve the workflow for users who rely on Docker Compose to orchestrate their services (e.g., Traefik, Nextcloud, Plex, etc.).
It would also make Lazydocker a more complete "single-pane-of-glass" tool for managing Docker environments without constantly switching back to the CLI.

davipro34 avatar Sep 06 '25 13:09 davipro34

If you press "?" while in the services tab in lazydocker you can see some frequently used commands and "U" says it spins up the current project. Is that what you are looking for?

Image

jack-oconnor-lrn avatar Sep 15 '25 13:09 jack-oconnor-lrn

I agree. I have multiple stacks in different folders (but all inside one parent folder), and I work with them separately (enter a folder, do something, move to another, and so on). Representing a stack as a separate entity that you could "dive into" and see the containers inside would be VERY convenient.

I think the list of all stacks can be automatically obtained from the labels of running containers, and it could also be added to a config file.

troman29 avatar Sep 16 '25 11:09 troman29

If you press "?" while in the services tab in lazydocker you can see some frequently used commands and "U" says it spins up the current project. Is that what you are looking for?

Image

I think the ask is to be able Up/Down any registered Compose stack, not just the one defined in the CWD. I was definitely surprised this was not supported.

bnwa avatar Oct 24 '25 18:10 bnwa