Docker build & push (production images)

SkillCloud & infra

Build and push OpenTranscribe production images (backend, lite backend, frontend, docs) to Docker Hub, multi-arch via the remote builder. Use when the user says "build the production images", "push to Docker Hub", "publish images", "multi-arch build", or is cutting a release that ships new container

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Docker build & push (production images) skill

What this skill tells your AI

The instructions your AI receives, as published by attevon-llc/opentranscribe in .claude/skills/docker-build-push/SKILL.md and read by ahel’s review.

Always use USE_REMOTE_BUILDER=true for multi-arch — without it ARM64 falls back to QEMU (2–3 hours vs 15–30 min via the Mac Studio builder).

USE_REMOTE_BUILDER=true ./scripts/docker-build-push.sh                    # both services
USE_REMOTE_BUILDER=true ./scripts/docker-build-push.sh backend|frontend   # one service
USE_REMOTE_BUILDER=true SKIP_SECURITY_SCAN=true ./scripts/docker-build-push.sh backend  # quick iteration
USE_REMOTE_BUILDER=true ./scripts/docker-build-push.sh auto               # auto-detect changed
PLATFORMS=linux/amd64 ./scripts/docker-build-push.sh backend              # single-arch (no remote needed)

Full docs: scripts/README.md.

Signals

GitHub stars
95
Forks
20
Last commit
Sep 2026

ahel review

  • S4info
    community integration — published by attevon-llc, not docker

Automated review, not a security audit. Ruleset v1.

Advanced
Catalog kind
skill
Gateway key
docker-build-push
Source
github.com/attevon-llc/opentranscribe