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

Unable to down non project containers #19

Open
svrana opened this issue Jun 1, 2019 · 1 comment
Open

Unable to down non project containers #19

svrana opened this issue Jun 1, 2019 · 1 comment
Milestone

Comments

@svrana
Copy link
Contributor

svrana commented Jun 1, 2019

When dev {project} down is run only the project container is shut down. Any other containers listed in the docker-compose files for the project are not brought down. This was intentional b/c dev doesn't really know the relationship between all the projects. Once issue #4 is resolved, flags can be added to the 'down' command to shut down all shared dependencies (probably should result in a warning that other dependent projects will also be shu down).

@svrana svrana changed the title Unable to bring stop non project containers Unable to down non project containers Jun 2, 2019
@svrana svrana added this to the .2 milestone Jun 2, 2019
@jerryzxliu
Copy link

want to point out that, if there's another running container B that depends on the dependencies of container A, dev down on A should not bring down the dependencies of A that are also dependencies of B

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

No branches or pull requests

2 participants