auto-update-daily-20260202

name: Docker description: Container management with Docker and Podman. USE WHEN building images, managing containers, working with compose files, debugging containers, managing networks/volumes, scanning for vulnerabilities, or optimizing images.

Docker

Comprehensive container management using Docker or Podman with intelligent runtime detection.

Features

  • Runtime Detection: Automatically detects and uses Docker or Podman
  • Compose Support: Works with docker-compose and podman-compose
  • Multi-Architecture: Build images for multiple platforms
  • Rootless Support: Handles Podman rootless mode
  • Security: Image vulnerability scanning and best practices
  • Optimization: Image size reduction and layer optimization

Workflow Routing

Workflow Trigger File
Build “build docker image”, “create dockerfile”, “build container image”, “build arm image”, “multi-arch build”, “cross-platform image”, “reduce image size”, “optimize dockerfile”, “smaller image”, “buildx”, “buildah”, “multi-stage build” workflows/Build.md
Run “start container”, “stop container”, “container status”, “list containers”, “container logs”, “exec into container”, “debug container”, “docker compose”, “compose up”, “manage compose services”, “restart container”, “inspect container”, “attach to container” workflows/Run.md
Infrastructure “create network”, “list networks”, “connect container to network”, “create volume”, “list volumes”, “mount volume”, “push image”, “pull image”, “login to registry”, “registry auth”, “docker network”, “docker volume” workflows/Infrastructure.md
Maintain “clean docker”, “remove unused images”, “prune containers”, “scan image”, “check vulnerabilities”, “security scan”, “trivy”, “grype”, “docker system prune”, “cleanup resources” workflows/Maintain.md

Docker vs Podman

This skill works seamlessly with both runtimes:

Docker

  • Daemon-based architecture
  • Requires root or docker group membership
  • Native docker-compose support
  • Standard on most systems

Podman

  • Daemonless, fork-exec model
  • Rootless by default
  • Drop-in Docker CLI replacement
  • Systemd integration for containers
  • Support for pods (Kubernetes-like)

The skill automatically detects which runtime is available and adjusts commands accordingly.

Runtime Selection

By default, the skill auto-detects available runtimes (prefers Podman for rootless). You can explicitly choose a runtime in your prompts:

Explicit mentions (natural language):

  • “Use Docker to build this image”
  • “Build this image with Podman”
  • “Using Docker, start the container”
  • “With Podman, create a volume”

When you mention a specific runtime, the skill will use that runtime exclusively for the operation.

Auto-detection behavior:

  1. Checks for Podman first (rootless preference)
  2. Falls back to Docker if Podman not found
  3. Errors if neither is available

When both are installed: You have both runtimes available, so you can choose based on your needs:

  • Podman: Rootless, daemonless, pods support
  • Docker: Mature ecosystem, wider adoption, better tooling

Examples

Example 1: Build a container image

User: "Build a Docker image from the Dockerfile in the current directory"
→ Invokes Build workflow
→ Detects Docker/Podman
→ Builds image with best practices
→ Tags appropriately

Example 2: Debug a running container

User: "Show me the logs for the nginx container"
→ Invokes Run workflow
→ Retrieves and displays logs
→ Offers to exec into container if needed

Example 3: Clean up unused resources

User: "Clean up old Docker images and containers"
→ Invokes Maintain workflow
→ Shows what will be removed
→ Prunes unused resources safely

Example 4: Multi-architecture build

User: "Build this image for both AMD64 and ARM64"
→ Invokes Build workflow
→ Sets up buildx/buildah
→ Builds for multiple platforms
→ Pushes to registry with manifest

Example 5: Explicit runtime selection

User: "Use Docker to build this image"
→ Invokes Build workflow
→ Forces Docker runtime (--runtime docker)
→ Uses Docker-specific features if needed

User: "With Podman, start a rootless container"
→ Invokes Run workflow
→ Forces Podman runtime (--runtime podman)
→ Uses Podman rootless mode

Best Practices

Dockerfile

  • Use multi-stage builds
  • Minimize layers
  • Use specific base image tags
  • Run as non-root user
  • Use .dockerignore

Security

  • Scan images regularly
  • Keep base images updated
  • Don’t embed secrets
  • Use minimal base images
  • Follow least privilege principle

Performance

  • Leverage build cache
  • Order layers by change frequency
  • Use smaller base images
  • Clean up in same layer

Tools

  • DetectRuntime.sh: Detects Docker or Podman and returns runtime info