Docs Self-Managed Reference rpk Commands rpk container rpk container status This is documentation for Self-Managed v24.1. To view the latest available version of the docs, see v24.2. rpk container status Get a local container’s status. Usage rpk container status [flags] Example If you’re following QuickStart - Deploy Redpanda to Docker with Three Nodes, you can run rpk container status to see more information about your containers: $ rpk container status NODE-ID STATUS KAFKA-ADDRESS ADMIN-ADDRESS PROXY-ADDRESS 0 running 127.0.0.1:34189 127.0.0.1:36539 127.0.0.1:41235 1 running 127.0.0.1:45523 127.0.0.1:35135 127.0.0.1:40155 2 running 127.0.0.1:37223 127.0.0.1:42571 127.0.0.1:41907 You can use rpk to interact with this cluster. For example: rpk cluster info --brokers 127.0.0.1:34189,127.0.0.1:45523,127.0.0.1:37223 You may also set an environment variable with the comma-separated list of broker addresses: export REDPANDA_BROKERS="127.0.0.1:34189,127.0.0.1:45523,127.0.0.1:37223" rpk cluster info Flags Value Type Description -h, --help - Help for status. --config string Redpanda or rpk config file; default search paths are /var/lib/redpanda/.config/rpk/rpk.yaml, $PWD/redpanda.yaml, and /etc/redpanda/redpanda.yaml. -X, --config-opt stringArray Override rpk configuration settings. See rpk -X or execute rpk -X help for inline detail or rpk -X list for terser detail. --profile string Profile to use. See rpk profile for more details. -v, --verbose - Enable verbose logging. Back to top × Simple online edits For simple changes, such as fixing a typo, you can edit the content directly on GitHub. Edit on GitHub Or, open an issue to let us know about something that you want us to change. Open an issue Contribution guide For extensive content updates, or if you prefer to work locally, read our contribution guide . Was this helpful? thumb_up thumb_down group Ask in the community mail Share your feedback group_add Make a contribution rpk container start rpk container stop