← Back to Skills Marketplace
ericlooi504

Docker Ops

by ericlooi504 · GitHub ↗ · v1.0.2 · MIT-0
cross-platform ⚠ suspicious
11
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install docker-ops-toolkit
Description
Docker container lifecycle management, health checks, log analysis, cleanup, compose orchestration, and troubleshooting. Use when Codex needs to manage Docke...
README (SKILL.md)

Docker Ops

Overview

Docker container lifecycle management, health checks, log analysis, cleanup, compose orchestration, and troubleshooting. Use when Codex needs to manage Docker containers, debug running services, or clean up Docker resources.

Quick Start

Prerequisites

  • Docker Engine (docker CLI)
  • docker compose plugin (for compose)

Check what's running

docker ps -a --format 'table {{.Names}}	{{.Status}}	{{.Ports}}	{{.Image}}'
docker stats --no-stream                   # live resource usage

Inspect a container

docker inspect \x3Ccontainer> | jq '.[0].State'   # status, exit code, health
docker inspect \x3Ccontainer> --format '{{json .Mounts}}' | jq .

Logs analysis

docker logs \x3Ccontainer> --tail 100 --since 5m
# Use docker-log-inspector.py for filtering:
python3 scripts/docker-log-inspector.py \x3Ccontainer> --since 30m --filter ERROR --summary

Clean up unused resources

# Standard cleanup
bash scripts/docker-cleanup.sh
# Aggressive cleanup (removes volumes + build cache)
bash scripts/docker-cleanup.sh --aggressive
# Preview only
bash scripts/docker-cleanup.sh --dry-run

Health check

bash scripts/docker-health.sh                     # all containers
bash scripts/docker-health.sh \x3Ccontainer-name>    # single container

Common Tasks

Docker Compose workflows

docker compose up -d                      # start services
docker compose down -v                    # stop + remove volumes
docker compose logs -f --tail 50          # follow logs
docker compose ps                         # status
docker compose exec \x3Cservice> sh          # shell into a service
docker compose build --no-cache \x3Csvc>     # rebuild without cache
docker compose restart \x3Cservice>          # restart one service

Port conflicts

# Find what's using a port
sudo lsof -i :\x3Cport>
docker ps --format '{{.Names}} {{.Ports}}' | grep \x3Cport>
# Fix: change port mapping in docker-compose.yml or stop conflicting container

Resource limits and OOM

docker inspect \x3Ccontainer> --format '{{json .HostConfig.Memory}}'
docker stats \x3Ccontainer> --no-stream
# Fix: add to docker-compose.yml
#   deploy:
#     resources:
#       limits:
#         memory: 512M
#         cpus: '0.5'

Image management

docker images --format 'table {{.Repository}}	{{.Tag}}	{{.Size}}	{{.CreatedSince}}'
docker image prune -a                    # remove all unused images
docker rmi \x3Cimage-id>                    # remove specific image
docker pull \x3Cimage>:\x3Ctag>                # update image
docker build -t \x3Cname>:\x3Ctag> .           # build
docker build --no-cache -t \x3Cname> .      # force rebuild

Network troubleshooting

docker network ls
docker network inspect \x3Cnetwork>
# Test connectivity from a container:
docker exec \x3Ccontainer> ping \x3Cother-container>
docker exec \x3Ccontainer> curl -v http://service:port

Data volumes

docker volume ls
docker volume inspect \x3Cvolume>
docker run --rm -v \x3Cvolume>:/data alpine ls -la /data   # inspect volume contents

Troubleshooting

Container exits immediately

docker logs \x3Ccontainer>                   # check exit reason
docker inspect \x3Ccontainer> --format '{{.State.ExitCode}}'
# Common causes:
#   0  → clean exit (expected?)
#   1  → application error (check logs)
#   137 → SIGKILL (OOM kill)
#   139 → segfault

Disk space issues

docker system df                          # disk overview
du -sh /var/lib/docker/containers/        # container overlay sizes
bash scripts/docker-cleanup.sh --aggressive

Container can't resolve DNS

docker exec \x3Ccontainer> cat /etc/resolv.conf
# Fix: add to docker-compose.yml
#   dns:
#     - 8.8.8.8
#     - 1.1.1.1

Permission errors

# Add user to docker group
sudo usermod -aG docker $USER && newgrp docker

Resources

  • scripts/docker-cleanup.sh — Interactive cleanup with dry-run mode
  • scripts/docker-health.sh — Multi-container health overview
  • scripts/docker-log-inspector.py — Regex filtering + severity summary for logs
  • references/compose-patterns.md — Docker Compose patterns and recipes
Usage Guidance
Install only if you want the agent to help manage Docker on this machine. Ask before running cleanup, `docker compose down -v`, or any sudo/group-membership changes, and prefer dry-run or inspection commands before deleting resources. Treat container logs as untrusted and potentially sensitive.
Capability Analysis
Type: OpenClaw Skill Name: docker-ops-toolkit Version: 1.0.2 The bundle provides standard Docker management utilities for container lifecycle management, health monitoring, and log analysis. The included scripts (docker-cleanup.sh, docker-health.sh, and docker-log-inspector.py) perform their stated functions using standard Docker CLI commands without any evidence of data exfiltration, persistence mechanisms, or malicious prompt injection.
Capability Assessment
Purpose & Capability
The described purpose matches the artifacts: Docker lifecycle, health checks, log inspection, cleanup, and Compose troubleshooting. Some commands are inherently high-impact, such as pruning resources and removing volumes, but they are disclosed and aligned with Docker operations.
Instruction Scope
The instructions present command examples for inspection, cleanup, Compose operations, and troubleshooting. Destructive examples such as aggressive cleanup and `docker compose down -v` are visible rather than hidden, but users should approve them explicitly before use.
Install Mechanism
There is no install spec and no automatic setup, but the metadata under-declares the Docker and Compose CLI prerequisites that SKILL.md requires. This is a metadata gap, not evidence of hidden installation.
Credentials
Docker daemon operations are proportionate to the stated purpose, but Docker access can inspect logs, execute commands in containers, and remove local Docker resources.
Persistence & Privilege
The skill does not create background persistence, but it includes a troubleshooting command to add the user to the Docker group, which is a persistent privilege change.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install docker-ops-toolkit
  3. After installation, invoke the skill by name or use /docker-ops-toolkit
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
Fix: docker-health.sh now handles --help / -h flag
v1.0.1
Fix: docker-health.sh now handles --help flag properly
v1.0.0
Initial release: container management, health checks, log analysis, cleanup scripts, compose patterns
Metadata
Slug docker-ops-toolkit
Version 1.0.2
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 3
Frequently Asked Questions

What is Docker Ops?

Docker container lifecycle management, health checks, log analysis, cleanup, compose orchestration, and troubleshooting. Use when Codex needs to manage Docke... It is an AI Agent Skill for Claude Code / OpenClaw, with 11 downloads so far.

How do I install Docker Ops?

Run "/install docker-ops-toolkit" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Docker Ops free?

Yes, Docker Ops is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Docker Ops support?

Docker Ops is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Docker Ops?

It is built and maintained by ericlooi504 (@ericlooi504); the current version is v1.0.2.

💬 Comments