5.4 Docker and Podman
A container cannot see the agents on your machine.
Agents are discovered by reading the home directories and install paths of the machine Gateway runs on, and inside a container that is the container's own filesystem. So Agents, Skills, MCP & Prompts and agent monitoring stay empty there — and the pages say so, rather than pretending nothing is installed.
Everything that does not depend on the host works normally: Providers, Authenticity and LLM Records.
So: run the one-command install on the machine whose agents you want to watch, and use a container when Gateway is only a model endpoint for other machines.
Running it
No image is published, so the compose file builds one from a checkout of this repository:
docker compose up -dPodman reads the same file:
podman compose up -dEither way:
- The UI is on http://localhost:17000.
- The SQLite database lives in a named volume that survives
down. conf/app.confis mounted from the repository, so the settings it seeds can be edited before the first start without rebuilding the image.
If it serves other machines
A container is usually reachable from outside the host, which is exactly the case 5.2 is about: change the admin password, and send the relay token with every request to /v1.
5.3 Backups and cloud sync
A backup is a snapshot of the configuration, written beside the database rather than inside it, so it survives the database it was taken from.
5.5 Updating, stopping and removing
All of them work from any directory: the command is a wrapper that always starts Gateway in its install directory, where its data lives.