We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What are your thoughts on having a docker file that can start with a specific role -Either a coordinator or historical or broker etc.
So this way we can use the same image in production depending on the role type. So basically it will be
docker start coordinator 8081 docker start all (could start everything up)
What do you think @gianm ?
The text was updated successfully, but these errors were encountered:
Definitely sounds useful.
Sorry, something went wrong.
Hey @gianm @niketh I amde an attempt to make a docker image for the same. Docker.zip
You can build the image using the Dockerfile in the zip.
You can run components like this $ docker run druid start historical
$ docker run druid start historical
the image also has a zookeeper in it. we can also run zookeeper $ docker run druid start zookeeper
$ docker run druid start zookeeper
To fire up all components for a quick start run $ docker run druid start all
$ docker run druid start all
The common.runtime.properties is also take out so even external system can be configured
@niketh I have sent a pull request for the same. check it out and let me know
No branches or pull requests
What are your thoughts on having a docker file that can start with a specific role -Either a coordinator or historical or broker etc.
So this way we can use the same image in production depending on the role type. So basically it will be
What do you think @gianm ?
The text was updated successfully, but these errors were encountered: