Skip to content

Stopping existing containers when docker-compose changes after a rerun of stack_box #5

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

Open
strangest-quark opened this issue Mar 17, 2020 · 0 comments
Labels

Comments

@strangest-quark
Copy link
Collaborator

We lose track of existing containers when we rerun stackbox keeping the existing containers. Two possible solutions.

Also results in listing these existing containers as up in the final stackbox.sh logs

Add a check before new docker compose generation for existing containers with the prefix stackbox_ in their names to stop before bringing up new ones
Or add a stackdown sh to bring down containers

@strangest-quark strangest-quark added bug Something isn't working good first issue Good for newcomers labels Mar 17, 2020
@strangest-quark strangest-quark self-assigned this Mar 17, 2020
@strangest-quark strangest-quark removed their assignment Mar 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant