Scope containers to project

[igbanam]

Is your feature request related to a problem? Please describe.
I wouldn't say it's a problem per se. The lazydoccker UI has a "project" section which rightly identifies the folder I'm in. But in the containers section, I am seeing containers belonging to other projects; albeit exited. Looks like the containers are not scoped to the project.

Describe the solution you'd like
Would be nice to see containers scoped to the project. If lazydocker is a replacement for Docker Desktop and the like, then this may be a non-issue.

Describe alternatives you've considered
I currently use OrbStack; but this is not scoped to projects. It's just a faster Docker Desktop, as at when I made the switch

Additional context
This is my first foray into lazydocker — literally first run. So if there's some config to scope this, please share. Thanks!

[peauc]

I've encountered this issue too, but in reverse. Most of the time, I actually want to see all my containers and only switch to project view when working on a specific part of the stack.

I think LazyDocker could benefit from having two modes:

1. All Containers View: Displays all containers without the project view, allowing more space for contexts, logs, etc.
2. Project View: Shows only the containers related to a specific project, with a menu to switch between projects based on existing container projects.

[cardin]

By "folder I'm in", I presume you're referring to the Compose context in the current folder? Being that Docker Containers are otherwise not inherent to any particular folder.

There is a Service View, that scopes the containers to those of the current Compose context. And there's a Standalone Containers View that shows everything else excluding those in Service View.

[jesseduffield]

Should be fixed by #774 (v0.25.0). Let me know if the issue persists: that PR was intended to fix a bunch of issues in one go.