docker-multiarch-offline-handoff

What problem does it solve?

This Skill solves the critical pain point of distributing containerized applications that require support for both x86_64 (amd64) and aarch64 (arm64) architectures to customers or servers with no access to a Docker registry (including Docker Hub, ECR, or local registries), a common constraint for air-gapped, restricted-network, or offline deployment environments.

Core Features & Use Cases

• Per-architecture tarball generation: Builds separate, loadable Docker image tarballs for each target architecture, avoiding the broken manifest list workflow that requires registry access.
• Auto-detecting customer install script: Includes a drop-in install script that automatically identifies the target machine's architecture via uname -m, loads the correct tarball, and re-tags images to match standard compose file references.
• Edge case guardrails: Captures and resolves common pitfalls including QEMU cross-compilation slowness, missing curl in alpine-based healthchecks, and post-load image tagging mismatches that cause silent compose failures.
• Use Case: A SaaS vendor shipping a containerized product to enterprise customers with mixed x86 server and ARM edge device fleets that have no outbound access to public registries.

Quick Start

Use the docker-multiarch-offline-handoff skill to generate per-architecture Docker image tarballs for your multi-service application and a customer install script that automatically loads the correct images for the target machine's architecture.