> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alginte.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Run with Docker

> Run the Alginte Docker image, including how to reach a broker on a Docker network.

The Docker image is the primary distribution channel — it bundles its own JRE and the
web UI, so there is nothing else to install.

```shell theme={null}
docker pull alginte/alginte:latest
docker run -p 8888:8888 \
  -e SPRING_KAFKA_BOOTSTRAPSERVERS=<kafka-host>:9092 \
  alginte/alginte:latest          # serve on http://localhost:8888
```

<Info>
  Alginte serves on port **8888**. Map it with `-p 8888:8888` (or `-p <host>:8888`).
</Info>

## Reaching a broker on a Docker network

<Warning>
  Inside a container, `localhost` refers to the **Alginte container itself** — not your
  host and not the broker. Pointing `SPRING_KAFKA_BOOTSTRAPSERVERS` at `localhost:9092`
  fails: the address resolves to the container, and even reaching the broker, a broker
  that advertises `localhost:9092` will be re-dialed inside Alginte's own container.
  This is the standard Kafka dual-listener trap.
</Warning>

If your broker runs in Docker Compose, join Alginte to the same network and use the
broker's **internal** service name and listener. Find the network with
`docker network ls` (usually `<compose-dir>_default`):

```shell theme={null}
docker run -p 8888:8888 \
  --network docker_default \
  -e SPRING_KAFKA_BOOTSTRAPSERVERS=broker:29092 \
  alginte/alginte:latest
```

To also wire the Confluent components, override their hosts to the Compose service names:

```shell theme={null}
docker run -p 8888:8888 \
  --network docker_default \
  -e SPRING_KAFKA_BOOTSTRAPSERVERS=broker:29092 \
  -e ALGINTE_KAFKACONNECTHOST=http://connect:8083/ \
  -e ALGINTE_KAFKASCHEMAREGISTRYHOST=http://schema-registry:8081/ \
  -e ALGINTE_KSQLDBHOST=ksqldb-server \
  alginte/alginte:latest
```

<Note>
  Env-var spelling matters. Spring relaxed binding **removes the dashes** from Alginte
  properties: `alginte.kafka-connect-host` becomes `ALGINTE_KAFKACONNECTHOST` (an
  underscore in place of the dash would bind a different property and be silently
  ignored). See [Configuration](/operate/configuration).
</Note>

## Escape hatch: skip the startup check

The fail-fast connectivity check can be disabled if you need the UI to start before the
broker is up:

```shell theme={null}
-e ALGINTE_STARTUPCONNECTIVITYCHECK_ENABLED=false
```