Skip to content

Hide project/services panels when not in a docker-compose project directory#776

Draft
Copilot wants to merge 2 commits intomasterfrom
copilot/disable-forced-project-view
Draft

Hide project/services panels when not in a docker-compose project directory#776
Copilot wants to merge 2 commits intomasterfrom
copilot/disable-forced-project-view

Conversation

Copy link

Copilot AI commented Mar 15, 2026

v0.25's multi-project discovery caused the Projects and Services panels to always appear, even when launched outside a compose project. Containers were also filtered to the first discovered project, making other running containers invisible.

Changes

  • project_panel.go: Added Hide returning !InDockerComposeProject — Projects panel only appears when inside a compose directory.

  • services_panel.go: Simplified Hide from !InDockerComposeProject && len(services) == 0 to !InDockerComposeProject. The old check caused the panel to appear whenever other compose containers were running on the system.

  • containers_panel.go: Project-based filtering now only applies when InDockerComposeProject is true — outside a compose project, all containers are shown in a flat list regardless of their compose project label.

  • arrangement.go: The compact-size treatment (Size: 3) for the first side panel was unconditional. Now it only applies when sideWindowNames[0] == "project", preventing the Containers panel from being squashed to 3 lines when the Projects panel is hidden.

Original prompt

This section details on the original issue you should resolve

<issue_title>Disable forced Project view</issue_title>
<issue_description>Is your feature request related to a problem? Please describe.
Before v25 if I run lazydocker in a "non project" folder I was able to see all running containers on the system in the container[3] view, regardless if they belong to a docker-compose project or not and the Services [2] panel was hidden. If i run it from inside a docker-compose project folder I would see the containers of the compose project in the Services[2] Panel and all others in the containers[3] panel.

Now I am no longer able to see all containers on the system at once, no matter in which folder I run lazydocker.
Also now the "Services" panel is always visible which adds yet another panel to the already overcrowded left side (see also #513)

Describe the solution you'd like
A way to disable the "Project" functionality if lazydocker is not run inside a project folder and have all containers be visible in a flat list in panel [3] like it was possible in v24. As shown in the Github Project's own readme/demo https://github.com/jesseduffield/lazydocker/blob/master/docs/resources/demo3.gif

</issue_description>

Comments on the Issue (you are @copilot in this section)


📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

Co-authored-by: jesseduffield <8456633+jesseduffield@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix forced Project view in lazydocker Hide project/services panels when not in a docker-compose project directory Mar 15, 2026
Copilot AI requested a review from jesseduffield March 15, 2026 22:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Disable forced Project view

2 participants