Docker section

The Docker section (right rail) gathers everything related to the Docker daemon and Aseptic’s containers.

Daemon

Shows the Docker daemon’s status: connected, starting or not connected. If it isn’t started, Start Docker launches Docker Desktop and waits for it to respond.

Docker is needed to launch the infrastructure and to run micros in container mode. In the app, starting Docker is a manual action; the CLI (aseptic start) starts it on its own.

Infrastructure

• Start infrastructure — launches only the infra the selected scenario declares (Kafka, Redis, Postgres…), without the micros.
• Stop infrastructure — docker compose down of the common infra. It can’t be stopped with the scenario running (stop it first).

Infrastructure console and messages

Each running infrastructure service has its own “⋮” menu with what you can do inside its container:

• Open console — opens the system terminal with psql (Postgres) or redis-cli (Redis) already connected, using the user and database the container itself declares. From the CLI: aseptic console postgres.
• Kafka messages — reads a topic (from the beginning or only what arrives) and publishes messages with an optional key. It uses the tools in the Kafka image itself, older versions included. From the CLI: aseptic kafka topics, aseptic kafka consume <topic> and aseptic kafka produce <topic> <message>.

Reading takes a while: it returns after 50 messages or 10 seconds without new ones, plus the time the consumer takes to join its group.

Containers

Lists the running aseptic-* containers with their status, health and ports.

• Remove orphans — deletes the aseptic-* containers left over (for example after an abrupt shutdown).

From the CLI

aseptic docker status, docker start, aseptic infra-up, infra-down, containers, docker-clean.