rpk container start
Start a local container cluster.
Example
If you’re following QuickStart - Deploy Redpanda to Docker with Three Nodes, you can run rpk container start -n 3
to start your containers:
$ rpk container start -n 3
Starting cluster
Waiting for the cluster to be ready...
Cluster started!
NODE-ID STATUS KAFKA-ADDRESS ADMIN-ADDRESS PROXY-ADDRESS
0 running 127.0.0.1:45841 127.0.0.1:40705 127.0.0.1:36875
1 running 127.0.0.1:42467 127.0.0.1:38959 127.0.0.1:37665
2 running 127.0.0.1:44941 127.0.0.1:46047 127.0.0.1:45783
You can use rpk to interact with this cluster. E.g:
rpk cluster info --brokers 127.0.0.1:45841,127.0.0.1:42467,127.0.0.1:44941
You may also set an environment variable with the comma-separated list of
broker addresses:
export REDPANDA_BROKERS="127.0.0.1:45841,127.0.0.1:42467,127.0.0.1:44941"
rpk cluster info
Flags
Value | Type | Description |
---|---|---|
|
- |
Help for start. |
|
string |
An arbitrary container image to use (default |
|
- |
If true, |
|
- |
Force pull the container image used. |
|
- |
uint The number of brokers to start (default 1). |
|
- |
uint The amount of times to check for the cluster before considering it unstable and exiting. (default 10). |
|
string |
Redpanda or rpk config file; default search paths are |
|
stringArray |
Override |
|
string |
Profile to use. See |
|
- |
Enable verbose logging. |