Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Termix-SSH/Termix/llms.txt

Use this file to discover all available pages before exploring further.

Docker Management in Termix gives you visibility and basic control over Docker containers running on your SSH hosts. It is designed for day-to-day container management tasks: checking what is running, reading logs, restarting a container, or dropping into one for a quick inspection — without needing a separate tool open.
Docker management in Termix is not a replacement for Portainer or Dockge. It covers simple container management — controlling running containers and inspecting their state. Creating and composing containers is outside its scope.

What you can do

Container lifecycle

Start, stop, pause, and remove containers. Actions are executed over the existing SSH connection using Docker CLI commands.

Real-time stats

View live CPU usage, memory consumption, and network I/O for running containers — equivalent to docker stats in your terminal.

Container logs

Tail and browse logs for any container. Review recent output without opening a separate terminal.

Exec terminal

Open an interactive docker exec terminal session inside a running container. Run commands inside the container directly from the browser.

Enabling Docker management

Docker management must be enabled individually for each host where you want to use it.
1

Open host settings

Navigate to the host you want to manage and open its settings panel.
2

Enable Docker

Toggle on the Docker management option. This authorizes Termix to run Docker commands on that host via SSH.
3

Connect and manage

Open the Docker tab for the host. Termix establishes an SSH session and lists the running and stopped containers.
If Docker management is not enabled for a host, attempts to open the Docker panel for that host will be rejected. Enable it in host settings first.
The exec terminal is particularly useful for inspecting container internals — checking configuration files, environment variables, or running a quick diagnostic command — without needing to SSH to the host separately and remember the container name.

Build docs developers (and LLMs) love