Omnigent Docker Compose Deploy

What it does

When your agent uses it

• Standing up the Omnigent server locally or on a VPS with Docker
• Debugging why the Omnigent compose stack won't start on a host
• Building the separate host image used by remote sandbox providers

Example prompts

• “Bring up the Omnigent docker compose stack on this VPS.”
• “Build the host image target instead of the server runtime image.”
• “The compose stack won't connect to Postgres, help me debug it.”

Requirements

• Docker and Docker Compose

What it can do on your machine

Read from SKILL.md and the folder at commit fa1dbe6. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships script files (Shell and Python), which the agent can run.

  Shell commands in SKILL.md call:

  • docker
  • npm
  • uv

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use docker, npm and uv, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • POSTGRES_PASSWORD

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Omnigent Docker Compose Deploy loads about 1.3k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 553 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~90

When it runs · the whole SKILL.md, loaded when a task matches

~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:33

  cp .env.example .env             # edit POSTGRES_PASSWORD at minimum

• NoteMentions a .env fileSKILL.md:63

  If you change it in `.env`, you need `docker compose down -v` before

• NoteMentions a .env fileSKILL.md:73

  ailed` | `POSTGRES_PASSWORD` changed in `.env` after the data volume was initialized | `docker compose down -v` then `up

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from omnigent-ai/omnigent at commit fa1dbe6, republished under its Apache-2.0 licence (© omnigent-ai). 553 words, ~1,250 tokens.

name

deploy-docker-compose

description

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack for a new platform.

cd deploy/docker
cp .env.example .env             # edit POSTGRES_PASSWORD at minimum
docker compose up -d --build
docker compose logs -f omnigent   # Ctrl-C when you see "Uvicorn running"

# Force a clean rebuild after a Dockerfile or source change
docker compose build --no-cache omnigent

# Reset everything (drops the DB + artifact volumes)
docker compose down -v
docker compose up -d --build

© omnigent-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 13 other files in deploy/docker of omnigent-ai/omnigent.

• SKILL.md
• .env.example
• Caddyfile
• Dockerfile
• Dockerfile.dockerignore
• Dockerfile.prebuilt
• Dockerfile.ubi
• README.md
• bootstrap.sh
• config.yaml.example
• docker-compose.https.yaml
• docker-compose.yaml
• entrypoint.py
• install-harness-cli.sh

Open the folder on GitHubat commit fa1dbe6