Build multi-arch Docker images with BuildKit and push to ghcr.io.
npx skills add https://github.com/erfianugrah/dotfiles --skill docker-erfianugrah
Please help me install this Agent Skill. Skill: docker Source: https://github.com/erfianugrah/dotfiles/tree/main/.pi/agent/skills/docker Command: npx skills add https://github.com/erfianugrah/dotfiles --skill docker-erfianugrah
It solves the problem of slow, opaque, and error-prone Docker image builds and deployments by giving you a repeatable way to author Dockerfiles, build multi-arch images, and verify what you actually shipped.
Use case example: You need to ship a multi-arch release of a service to ghcr.io while keeping builds fast—this skill guides you to structure the Dockerfile for cache reuse, build with buildx using registry cache, push properly tagged images, and then inspect layers/manifests if runtime behavior differs from expectations.
Ask the AI to help you write an optimized multi-stage Dockerfile using BuildKit cache mounts and secrets, then generate the exact buildx commands to build for linux/amd64 and linux/arm64 and push to ghcr.io with buildcache.
High-intent search queries and answers about installing and using this skill.
To build multi-arch Docker images and push to ghcr.io, use buildx with cache-to and cache-from flags for registry caching. This ensures reliable cross-platform builds while maintaining fast build speeds through BuildKit layer caching.
The best way to debug a Docker image is by inspecting its layer history, manifests, and configuration. You can use commands like image history, imagetools inspect, container logs, and exec inspection to investigate runtime failures and verify shipped contents.
BuildKit secrets and SSH mounts are used during Dockerfile builds by configuring cache mounts and SSH forwarding. This approach allows secure secret management during the build process without leaking sensitive data into the final image layers.
Yes, you can use buildx to load images locally by applying the correct buildx flags for load versus push. This distinction allows you to test images locally before pushing them to registries like ghcr.io for deployment.
Immutable tags should be used for Docker Compose deployments to ensure production-aware workflow discipline. This practice prevents accidental rollbacks or inconsistent environments while keeping optional rolling tags available for human convenience.
To optimize Docker layer ordering for faster build speeds, structure your Dockerfile to maximize cache reuse. Deterministic layer ordering combined with BuildKit cache mounts ensures efficient builds and reduces redundant processing during image creation.
kettleofketchupOptimize Docker builds with layer ordering, BuildKit cache mounts, and multi-stage patterns.
act70255Automates deployment workflows in modern CI/CD pipelines using GitOps and Kubernetes technologies.
HTRTanAutomate Docker image builds, tagging, registry pushes, and container lifecycle management.
kubiyabotAutomate Docker container and image management via the native Docker CLI.
