# rpk container start

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [streaming-full.txt](https://docs.redpanda.com/streaming-full.txt)

---
title: rpk container start
latest-redpanda-tag: v26.2.1
latest-console-tag: v3.10.0
latest-operator-version: v26.2.2
# EOL = End-of-Life (support lifecycle status)
page-is-nearing-eol: "false"
page-is-past-eol: "false"
page-eol-date: July 28, 2027
latest-connect-version: 4.105.0
docname: rpk/rpk-container/rpk-container-start
page-component-name: streaming
page-version: "26.2"
page-component-version: "26.2"
page-component-title: Streaming
page-relative-src-path: rpk/rpk-container/rpk-container-start.adoc
page-edit-url: https://github.com/redpanda-data/docs/edit/main/modules/reference/pages/rpk/rpk-container/rpk-container-start.adoc
description: Start a local container cluster. This command uses Docker to initiate a local Redpanda container cluster, including Redpanda Console.
page-git-created-date: "2023-05-17"
page-git-modified-date: "2026-08-17"
support-status: supported
---

<!-- Source: https://docs.redpanda.com/streaming/current/reference/rpk/rpk-container/rpk-container-start.md -->

Start a local container cluster.

This command uses Docker to initiate a local Redpanda container cluster, including Redpanda Console. Use the `--nodes`/`-n` flag to specify the number of brokers.

The initial broker starts on default ports, with subsequent brokers' ports offset by 1000. You can use the listeners flag to specify ports:

-   `--kafka-ports`

-   `--admin-ports`

-   `--rpc-ports`

-   `--schema-registry-ports`

-   `--proxy-ports`

-   `--console-port`


Each flag accepts a comma-separated list of ports for your listeners. Use the `--any-port` flag to let `rpk` select random available ports for every listener on the host machine.

By default, this command uses the redpandadata/redpanda:latest and redpandadata/console:latest container images. You can specify a container image by using the `--image` flag.

In case of IP address pool conflict, you may specify a custom subnet and gateway using the `--subnet` and `--gateway` flags respectively.

## [](#usage)Usage

```bash
rpk container start [flags]
```

## [](#examples)Examples

This section provides examples of how to use `rpk container start`.

Start a three-broker cluster.

```bash
rpk container start -n 3
```

Start a single-broker cluster, selecting random ports for every listener.

```bash
rpk container start --any-port
```

Start a 3-broker cluster, selecting the seed kafka and console port only.

```bash
rpk container start --kafka-ports 9092 --console-port 8080
```

Start a three-broker cluster, specifying the Admin API port for each broker.

```bash
rpk container start --admin-ports 9644,9645,9646
```

## [](#flags)Flags

| Value | Type | Description |
| --- | --- | --- |
| --admin-ports | stringSlice | Redpanda Admin API ports to listen on; check help text for more information. |
| --any-port | bool | Opt in for any (random) ports in all listeners. |
| --console-image | string | An arbitrary Redpanda Console container image to use. |
| --console-port | string | Redpanda console ports to listen on; check help text for more information. |
| --gateway | string | Gateway IP address for the subnet. Must be in the subnet address range. |
| --image | string | An arbitrary Redpanda container image to use. |
| --kafka-ports | stringSlice | Kafka protocol ports to listen on; check help text for more information. |
| --no-profile | bool | If true, rpk will not create an rpk profile after creating a cluster. |
| -n, --nodes | uint | The number of brokers (nodes) to start. |
| --proxy-ports | stringSlice | HTTP Proxy ports to listen on; check help text for more information. |
| --pull | bool | Force pull the container image used. |
| --retries | uint | The number of times to check for the cluster before considering it unstable and exiting. |
| --rpc-ports | stringSlice | RPC ports to listen on; check help text for more information. |
| --schema-registry-ports | stringSlice | Schema Registry ports to listen on; check help text for more information. |
| --set | string | Redpanda configuration property to set upon start. Follows rpk redpanda config set format. |
| --subnet | string | Subnet to create the cluster network on. |

## [](#global-flags)Global flags

| Value | Type | Description |
| --- | --- | --- |
| --config | string | Redpanda or rpk config file; default search paths are ~/.config/rpk/rpk.yaml, $PWD/redpanda.yaml, and /etc/redpanda/redpanda.yaml. |
| -X, --config-opt | stringArray | Override rpk configuration settings; -X help for detail or -X list for terser detail. |
| --ignore-profile | bool | Ignore rpk.yaml and redpanda.yaml; use default settings. |
| --profile | string | rpk profile to use. |
| -v, --verbose | bool | Enable verbose logging. |

## [](#suggested-reading)Suggested reading

-   [Docker Hub](https://hub.docker.com/r/redpandadata/redpanda/tags)

-   [QuickStart - Deploy Redpanda to Docker with a Single Broker](https://docs.redpanda.com/streaming/current/get-started/quick-start/#tabs-1-single-brokers)

-   [QuickStart - Deploy Redpanda to Docker with Three Nodes](https://docs.redpanda.com/streaming/current/get-started/quick-start/#tabs-1-three-brokers)