-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
docker-compose base service, should it run? #9
Comments
Closed
Yeah, it should work. If there are any specific issues with it, let me know. I'm not particularly a docker-compose user, so this doesn't see much love. I'm happy for someone to contribute to it. |
mattrobenolt
added a commit
that referenced
this issue
Nov 11, 2016
This was meant to be closed with 177ed0e |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From reading the docker-compose.yml I get the impression that the base service is an abstract definition of config and the other services extend on it.
But docker-compose is happily starting 'base' and it runs the default command from the sentry:8.8-onbuild image. Or is it necessary to have this double django service running, once exposed and once running without being able to accept any connections?
There's a discussion on compose abstract services here.
docker/compose#1988
The text was updated successfully, but these errors were encountered: