# Docker Deploy

> Inspect repo, author Dockerfile/compose, long builds, run with a clear deploy report

- **Type:** Skill
- **Install:** `agentstack add skill-frontier-ai-next-mgarlbot-docker-deploy`
- **Verified:** Pending review
- **Seller:** [frontier-ai-next](https://agentstack.voostack.com/s/frontier-ai-next)
- **Installs:** 0
- **Category:** [Cloud & Infrastructure](https://agentstack.voostack.com/c/cloud-infrastructure)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [frontier-ai-next](https://github.com/frontier-ai-next)
- **Source:** https://github.com/frontier-ai-next/mgarlbot/tree/main/skills/docker_deploy

## Install

```sh
agentstack add skill-frontier-ai-next-mgarlbot-docker-deploy
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

## Docker / Compose (test or prod stack)

Default chain: **inspect project → artifacts → validate config → build (may take long) → detached run for daemons → report**.

Work inside the target project tree (relative paths, `cd` into the service directory). With **HOST SHELL MODE** you may use absolute paths to other project roots on this machine.

If the user asks for **apt / OS-level commands on a remote VPS**, use skill **vps_host_ssh** (`ssh -F /data/.ssh/config vps '...'`), not local compose unless they explicitly want local only.

Public URL, Traefik/Nginx/frp, and REG.RU DNS — skills **ops_reverse_proxy** and **ops_dns_regru** (inspect proxy on the VPS first, then config).

Do not read or paste `.env`, keys, or tokens into the user-facing reply.

### Steps

1. **Analyze:** language/runtime from `pyproject.toml`, `package.json`, `go.mod`, `requirements.txt`, existing `Dockerfile`; entrypoint (CMD), ports, env var **names** only (not secret values).
2. **Files:** minimal working `Dockerfile`, sensible `.dockerignore`, `docker-compose.yml` if needed (`build`, `ports`, `env_file:` without baking secrets into the image).
3. **Config:** `docker compose config` (or `docker-compose config`) — fix until clean.
4. **Build:** `docker compose build` — iterate from logs; **do not treat a long build as failure** until the command exits with an error.
5. **Run:** for APIs/web/daemons use **`docker compose up -d`** so the session does not block on foreground logs unless the user asks for attached logs.
6. **Verify:** `docker compose ps` or `docker ps --filter name=...`; on failure `docker compose logs --tail=80 `.
7. **Report:** briefly what changed, service/container names, published ports, commands to verify and tail logs. State clearly e.g. “Deployed; check …”.

### Do not

- Put real secrets in `Dockerfile` or print `.env` contents.
- Suggest `rm -rf /`, chmod-the-world, or destructive actions outside the task.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [frontier-ai-next](https://github.com/frontier-ai-next)
- **Source:** [frontier-ai-next/mgarlbot](https://github.com/frontier-ai-next/mgarlbot)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** yes
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: flagged — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-frontier-ai-next-mgarlbot-docker-deploy
- Seller: https://agentstack.voostack.com/s/frontier-ai-next
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.