caigy opened a new issue, #74:
URL: https://github.com/apache/rocketmq-docker/issues/74
**FEATURE REQUEST**
When users run RocketMQ by docker images, the startup scripts must be
specified, e.g.:
```sh
docker run --name rmqnamesrv apache/rocketmq:4.9.2 sh mqnamesrv
```
It exposes too much details to users, for they should just need to specify
which module (like nameserver, broker, etc.) is expected to be started, instead
of the specific scripts.
I' like to add an entry point for RocketMQ docker image, making it more
simple to launch specific modules, without the loss of flexibility.
An entry-point script will be added, which supports:
- specifying custom commands to be run in docker, so that users can run
RocketMQ docker with specified command (like `sh mqbroker`) as the current way.
- specifying the module need to be launched, there're 2 ways:
- through docker command;
- through an environmental variable `NODE_ROLE`.
- The allowed values in the above 2 situations are as follows
(case-sensitive):
- `nameserver`
- `broker`
- `controller`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
