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

prefix docker containers names #161

Open
ppanero opened this issue Jul 24, 2019 · 2 comments
Open

prefix docker containers names #161

ppanero opened this issue Jul 24, 2019 · 2 comments

Comments

@ppanero
Copy link
Member

ppanero commented Jul 24, 2019

User Story

I cookiecut two instances and I want to run them both depending on which project I am working on.

Current result

The second docker-compose up will fail (containers already exist). This containers will need to be removed and recreated for the second project, because the ./scripts/setup will get denied in the DB (wrong credentials).

Expected result

I understand the services should be independent, but I don't want to have to change defaults of rabbit/redis/db/es for each instance. However, if the containers names(?) are prefixed with e.g. instance name this would not happen. The second docker-compose up would not fail and both could co-exist.

Possible drawback

End up with 20k services running, but is up to each one of us to control that I guess.

@lnielsen
Copy link
Member

You want them both running at the same time? Would you just get port conflicts?

@ppanero
Copy link
Member Author

ppanero commented Jul 31, 2019

True on the ports, but then if stopped, when creating the new ones, the name would still collide no?

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

No branches or pull requests

2 participants