Docker

Development

Control containers, images, and networks through plain language — Neotask harnesses OpenClaw to manage your Docker environment without memorizing CLI flags.

What You Can Do

Container Lifecycle

Run, stop, pause, resume, and remove containers by name or description. Neotask handles the flags — port bindings, volume mounts, environment variables, restart policies — so you can say "run the postgres container on port 5433 with a persistent volume" and get it done immediately via OpenClaw.

Image Management

Pull specific image tags from Docker Hub or private registries, list locally cached images sorted by size, and remove dangling layers. Build images from a Dockerfile path and tag them in one instruction.

Logs & Debugging

Retrieve the last N lines of container logs, stream live output, and filter by timestamp. Ask Neotask to summarize recent errors from a failing container and suggest likely causes based on the log content.

Networks & Volumes

Create named networks, connect or disconnect containers, and inspect network topology. List all volumes, see which are orphaned (no container attached), and remove them safely.

Docker Compose

Bring multi-service stacks up or down, scale specific services, and check the health of every container in a Compose project. Neotask can read your docker-compose.yml and explain what each service does.

Try Asking

  • "Start a Redis container named cache-dev on port 6380 with data persisted to ./redis-data"
  • "Show me the last 200 log lines from the api container and flag any lines containing 'error' or 'fatal'"
  • "List all running containers and their exposed ports in a clean table"
  • "Remove all stopped containers and dangling images to free up disk space"
  • "Pull postgres:16-alpine and start it with POSTGRES_PASSWORD=secret on port 5432"
  • "Which containers have been running for more than 7 days?"
  • "Inspect the network config for the frontend container — what network is it on and what's its IP?"
  • "Bring down the docker-compose stack in ./services/api and back it up with fresh images"

    • Pro Tips

  • Name your containers consistently (e.g., myapp-prod, myapp-dev) so Neotask can target the right one without ambiguity.
  • For complex run commands, describe the desired behavior (ports, volumes, env vars) rather than trying to dictate flags — OpenClaw generates the correct syntax.
  • Ask for a "disk usage summary" regularly — Docker layers accumulate fast and a prune query will show you exactly what can be reclaimed.
  • When debugging a failing container, ask for logs AND inspect output together so Neotask can correlate config issues with runtime errors.
  • Use "stream logs" for live debugging sessions; use "last N lines" when you want a snapshot to share or analyze.
  • For Compose projects, specify the project directory so Neotask knows which stack you mean when you have multiple.

    • Works Well With