You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ls is a great new feature for listing multiple projects, but it only shows project name, which could be custom if you use -p. Often, I'll start multiple versions of the same compose file with different project names, but it's hard to make sense of which project is which path as the CLI (and Docker Desktop Dashboard) don't show the compose file used.
Bonus points for also showing path to any overrides or layered compose files used in -f (or implicit with docker-compose.override.yml) using a -a or maybe --no-trunc.
I hope this would be an easy practice since the file path is listed in container labels.
ls
is a great new feature for listing multiple projects, but it only shows project name, which could be custom if you use-p
. Often, I'll start multiple versions of the same compose file with different project names, but it's hard to make sense of which project is which path as the CLI (and Docker Desktop Dashboard) don't show the compose file used.Bonus points for also showing path to any overrides or layered compose files used in -f (or implicit with docker-compose.override.yml) using a
-a
or maybe--no-trunc
.I hope this would be an easy practice since the file path is listed in container labels.
Current
ls
use:docker compose ls
Suggested compose file feature in
ls
command. Path could be just the raw path(s) from the labelThe text was updated successfully, but these errors were encountered: