agentleFS
Sign inStart free
CsHengCsHeng/agent-skills/skills/docker-multiarch-build/SKILL.md

docker-multiarch-build

Skill3 starsChanged 8 days agoMITView on GitHub

Use for multi-architecture Docker builds: buildx, amd64/arm64 images, Compose platform behavior, image validation, and cross-platform containers.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use multi-stage builds so the runtime image holds no build toolchain.

    line 12
  2. Very specific:

    Run the container as a non-root user where possible.

    line 14
  3. Very specific:

    Use docker compose, and write Compose files without a version field.

    line 16
  4. Very specific:

    Run builder selection, local build and push as three separate steps.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Docker Multi-Architecture Build

Build production images that run on both amd64 and arm64, using buildx and multi-stage Dockerfiles.

Steps

  1. Use multi-stage builds so the runtime image holds no build toolchain.
  2. Cross-compile compiled binaries (Go) with the BUILDPLATFORM, TARGETOS and TARGETARCH build args.
  3. Run the container as a non-root user where possible; container hardening follows security-guardrails.
  4. Validate per platform that the image starts and passes a simple health check (or document the health check as intentionally omitted). Load and run the native-platform image with --load; for the other platform, use a runtime already available and prefer cross-compilation over emulated builds.
  5. Use docker compose, and write Compose files without a version field.
  6. Run builder selection, local build and push as three separate steps; the commands are in references/buildx-commands.md, which applies whenever you run docker buildx.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free