container-build
Skill177 starsChanged 7 days agoApache-2.0View on GitHub
Build, check, and publish Apollo-Lite WheelOS development container images with Docker Buildx Bake.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- agent-evaluationSkill
- algorithm-developmentSkill
- buildSkill
- change-reviewSkill
- engineering-solution-designSkill
- interface-migrationSkill
- issue-localizationSkill
- lintSkill
- long-horizon-developmentSkill
- model-artifact-integrationSkill
- multi-repo-devSkill
- performance-optimizationSkill
- repository-agent-setupSkill
- simulation-regressionSkill
- test-impact-analysisSkill
- unified-core-runtimeSkill
- vendorSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill to build, check, or publish WheelOS development container images.
- Distinctive: line 16
Run commands from the repository root.
- Very specific: line 35
Use docker/build/build_docker.sh for safe Dockerfile checks and normal local builds.
- Very specific: line 63
Keep mutable dev-* tags for development.
- Distinctive: line 81
Stop at the first actionable build or check failure.
- Distinctive: line 84
Do not claim Orin runtime validation from QEMU or x86 builds.
- Distinctive: line 85
Do not publish mutable development tags as releases or overwrite published version tags.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Container Image Build
When
Use this skill to build, check, or publish WheelOS development container images. It covers image construction only; compiling Apollo source inside a running image is covered by Build.
Scope and prerequisites
- Run commands from the repository root.
- Docker Buildx Bake constructs the WheelOS images; it does not compile Apollo source.
- Supported targets:
dev-amd64-cpu-u22: x86_64 CPU, Ubuntu 22.04.dev-amd64-cuda-u22: x86_64 GPU, CUDA 12.8 / Ubuntu 22.04.dev-orin-jp621-l4t3643: Orin, JetPack 6.2.1 / L4T 36.4.3.
- The default Bake group builds x86 CPU and GPU. Build Orin on a native Orin/JetPack 6.2.1 host; QEMU cannot validate Jetson device-tree or GPU runtime requirements.
Workflow
Inspect the Bake graph before an unfamiliar or production build:
docker buildx bake -f docker/build/docker-bake.hcl --printUse
docker/build/build_docker.shfor safe Dockerfile checks and normal local builds. Supported legacy Dockerfile names include:bash docker/build/build_docker.sh -f dev.x86_64.cpu.dockerfile --check bash docker/build/build_docker.sh -f dev.x86_64.cpu.dockerfile bash docker/build/build_docker.sh -f dev.x86_64.cuda.dockerfile bash docker/build/build_docker.sh -f dev.aarch64.orin.dockerfile --geo cnThe wrapper selects one exporter: local Docker image store for local builds, registry for pushes, and cache-only for checks. Use
--checkrather than a raw Dockerfile check that could export an incomplete image to a local tag.- Select the registry and package mirrors with
--geo cn(Hangzhou registry and China mirrors) or--geo us(Docker Hub and public package sources).APOLLO_REPOoverrides the image repository. For a versioned validation build or release push, provide
--release-version. Add--pushonly when publishing:bash docker/build/build_docker.sh -f dev.x86_64.cpu.dockerfile \ --geo cn --release-version v1.2.3 bash docker/build/build_docker.sh -f dev.x86_64.cuda.dockerfile \ --geo cn --release-version v1.2.3 --pushKeep mutable
dev-*tags for development. Do not overwrite published version tags; promote the exact validated image digest instead of rebuilding for each environment.- Reuse the default Buildx cache.
--cleanis for cache diagnosis, not routine builds. BuildKit layer cache, HTTP artifact cache, and Bazel caches are separate;--cache-server URLselects the HTTP artifact cache andCACHE_REGISTRY=...configures shared BuildKit registry cache.
Acceptance
- The requested target builds or passes the wrapper's
--check. - Confirm the intended platform and versioned tag before publishing.
- A successful Orin cross-build is not proof of Jetson device-tree or GPU runtime correctness; require native Orin validation for those claims.
Failure handling
- Stop at the first actionable build or check failure. Inspect its output before changing options or retrying; do not disable cache or change registries as a blind workaround.
- Do not claim Orin runtime validation from QEMU or x86 builds.
- Do not publish mutable development tags as releases or overwrite published version tags.
Source of truth
docker/build/README.mddocker/build/docker-bake.hcldocker/build/build_docker.sh
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
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.

