Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switching projects #189

Open
dsc8x opened this issue Nov 18, 2019 · 10 comments
Open

Switching projects #189

dsc8x opened this issue Nov 18, 2019 · 10 comments

Comments

@dsc8x
Copy link

dsc8x commented Nov 18, 2019

Hey, first of all: Awesome project, many thanks for that! ❤️

I have one question: Is it possible to switch projects? For me only the last project that I started using docker-compose is shown and I am unable to figure out how to switch to other running projects 🤔

CleanShot 2019-11-18 at 15 48 39

@mjarkk
Copy link
Contributor

mjarkk commented Nov 18, 2019

I think it's showing this if docker compose shows information in your current dir.
So your current dir or one of it's parents might have a docker compose file that docker compose detects and lazy docker is showing that.

If that's not the case it might be that you have found a bug :)

@dsc8x
Copy link
Author

dsc8x commented Nov 20, 2019

If I run those two commands:

docker-compose up -p cpm-mcr
docker-compose up -p cpm-ms

Then lazydocker will only show me the containers created in the second project, which is exactly the cpm-ms scenario from the screenshot above.

The above example is pretty simplified, of course the different projects in real life have different env vars and configurations :)

@wesselvdv
Copy link

We're having this issue as well, when copying an existing docker-compose project as template for a new project, running lazydocker in that new project shows the original project images and containers.

@wesselvdv
Copy link

This is turning into a quite annoying issue, I currently have 2 folders that I cannot use at the same time due to Lazydocker not being able to differentiate between them. When running a container in the one folder, and moving to the other it'll briefly show the other folder its name, but then switch it to the former.

@saimonmoore
Copy link

Same here

@wesselvdv
Copy link

This seems to be caused by having running compose projects that have containers with exactly the same name. Seems the project prefix isn't taken into account.

@wesselvdv
Copy link

btw. seems this is a duplicate of #122

@milushov
Copy link

Having the same issue

@peauc
Copy link
Contributor

peauc commented Jun 8, 2024

We might need to rework how projects are handled or at least provide a way to change to recently opened projects

@lamnguyenx
Copy link

Please fix this issue! I usually run multiple docker-compose-based projects on the same machine.
I would be absolutely great if lazydocker could be "project-aware" just like docker-compose.
Right now, while the "Project" does show the correct "COMPOSE_PROJECT_NAME", the monitored services are only limited to the last started project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants