Skip to main content
The Docker image is the primary distribution channel — it bundles its own JRE and the web UI, so there is nothing else to install.
Alginte serves on port 8888. Map it with -p 8888:8888 (or -p <host>:8888).

​
Reaching a broker on a Docker network

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.
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):
To also wire the Confluent components, point their URLs at the Compose service names:
Every .url property takes a full URL. Naming details: Configuration.

​
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:

​
Running multiple containers

Each Alginte container is self-contained — run as many as you like against the same cluster; they don’t share state with each other. Details and the recovery story: Running multiple instances.

​
Beyond the first run

For production concerns — the security boundary and reverse proxies, mounting a properties file into the container, and what the image provides (non-root, health check, layered pulls) — see Production deployment.