ワンクリックで
docker-manage
Manage Docker containers on remote servers via NAVIG
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Manage Docker containers on remote servers via NAVIG
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Essential file system operations.
Common Git version control operations.
Upload, download, and edit files on remote servers via NAVIG
Summarize web pages, articles, YouTube videos, and documents using AI
Query and manage databases on remote servers via NAVIG
Check GitHub repos, CI status, PRs, and issues using the gh CLI
| name | docker-manage |
| description | Manage Docker containers on remote servers via NAVIG |
| user-invocable | true |
| navig-commands | ["navig docker ps","navig docker logs {container}","navig docker restart {container}","navig docker stats"] |
| examples | ["Show me Docker containers on production","Check logs for nginx container","Restart the postgres container","What containers are running?"] |
Manage Docker containers on remote servers using NAVIG commands.
User queries:
Command: navig docker ps
Response format:
🐳 Docker Containers on {host}:
✅ nginx-proxy (running, 2 days)
✅ postgres-db (running, 15 days)
✅ redis-cache (running, 15 days)
⚠️ backup-service (exited, 3 hours ago)
User queries:
Command: navig docker logs {container} --tail 50
Response format:
📋 Last 50 lines from {container}:
[2026-01-31 10:23:45] INFO: Server started on port 8080
[2026-01-31 10:24:12] INFO: Database connection established
[2026-01-31 10:25:33] ERROR: Failed to connect to Redis
[2026-01-31 10:25:34] INFO: Retrying Redis connection...
User queries:
Command: navig docker restart {container}
Response format:
🔄 Restarting {container}...
✅ Container restarted successfully!
Want me to check the logs to confirm it's healthy?
User queries:
Command: navig docker stats --no-stream
Response format:
📊 Container Resource Usage:
nginx-proxy: CPU: 2.5% | MEM: 128MB / 2GB (6%)
postgres-db: CPU: 15.3% | MEM: 1.2GB / 4GB (30%)
redis-cache: CPU: 1.1% | MEM: 256MB / 1GB (25%)
navig docker inspect {container} --format '{{.State.Health.Status}}'
⚠️ Destructive operation - Always confirm first!
navig run "docker container prune -f"
Response: "⚠️ This will remove all stopped containers. Are you sure? (yes/no)"
navig run "docker image prune -a -f"
Response: "🧹 Cleaned up unused Docker images. Freed: {size}"
If user mentions a specific application (nginx, postgres, n8n), check if a template exists:
navig template list
navig template show {template_name}
Example:
templates/n8n/template.yaml existsnavig run 'systemctl start docker'"navig run 'sudo docker ps'"Example 1: Quick Status Check
navig host use production && navig docker psExample 2: Troubleshooting
navig docker ps → check status → navig docker logs nginx --tail 100Example 3: Deployment
User: "Deploy Uptime Kuma on production"
Action: Check if template exists in templates/uptime-kuma/
Response: "Found Uptime Kuma template! I'll set up the Docker container. This will:
Proceed with deployment?"