Migrate and replace old Docker pipeline with docker-new

[xmfcx]

Summary

Replace the old docker/ pipeline (555-line monolith workflow, 18 component-split images, .env-driven config) with the new docker-new/ pipeline (ansible-first, unified images, HCL bake orchestration). The new pipeline runs side-by-side today and publishes to ghcr.io/autowarefoundation/autoware-new.

• The image structure and design are described in Simplify the docker images and workflows #6852. This issue tracks the migration roadmap and timeline.

• Related PR: ci: simplify docker #6851

Target: 2026-04-18

Phase 1: Land the new pipeline (side-by-side) -- Apr 11-14

New images publish to autoware-new. Old pipeline keeps running.

• PR 1 -- Dockerfiles + HCL + ansible playbook (Apr 11, open for review)
  • ansible/playbooks/autoware_requirements.yaml
  • docker-new/base.Dockerfile, core.Dockerfile, universe.Dockerfile
  • docker-new/docker-bake.hcl, docker-entrypoint.sh
  • docker-new/files/cyclonedds.xml, docker-new/README.md
  • feat(docker): add new Dockerfiles, HCL bake config, and ansible playbook #7004
• PR 2 -- CI build & push workflows (Apr 13, after PR 1 merges)
  • .github/workflows/docker-build-new.yaml (reusable)
  • .github/workflows/docker-build-pipeline-new.yaml (per-distro)
  • .github/workflows/docker-build-and-push-new.yaml (orchestrator)
  • ci(docker): add CI build and push workflows for docker-new #7012
  • fix(docker): include ROS distro in buildcache-new cache keys #7016
• PR 3 -- Health check workflow (Apr 14, after PR 2 merges)
  • Replaces .github/workflows/health-check.yaml to use docker-new pipeline
  • ci(docker): replace health-check workflow with docker-new pipeline #7014
• PR 4 -- GHCR buildcache cleanup workflow (Apr 14, parallel with PR 3)
  • .github/workflows/cleanup-autoware-buildcache.yaml
  • ci(docker): add cleanup workflow for autoware-buildcache-new #7015

Phase 2: Migrate consumers to new images -- Apr 15

Consumers inside the autoware repo must switch to new image names before the old pipeline can be removed.

Sub-repos (autoware_core, autoware_universe, autoware_tools, etc.) reference images by registry path from the main autoware repo. They do not need changes -- when the main repo switches to new images, sub-repos pick them up automatically. Test with autoware-new images in throwaway branches for confidence, but do not merge those branches.

• Dev containers (core-devel, universe-devel, universe-devel-cuda) -- add -jazzy suffix
• Scenario test CI (.github/workflows/scenario-test.yaml)
• Decide component images strategy (wait for Move component containers to openadkit repositories #6733, rewrite compose, or drop compose)
• Update or replace docker/run.sh and docker/build.sh
• Validation: test autoware_core, autoware_universe, and autoware_tools CI with new images in temporary branches (no merge needed)

Phase 3: Registry cutover -- Apr 16

• Decide final registry name (autoware-new vs take over autoware)
• If taking over autoware: update REGISTRY in workflows/HCL, publish deprecation notice for old tag format

Phase 4: Remove old pipeline -- Apr 16

• Delete docker/ tree (Dockerfiles, bake files, scripts, compose, .env files, README)
• Delete old CI workflows (docker-build-and-push.yaml, health-check.yaml, keep-build-cache-small.yaml)
• Check setup-dev-env.sh for remaining dependents, remove if safe
• Clean up old GHCR packages (autoware, autoware-tools, autoware-buildcache)

Phase 5: Rename docker-new/ to docker/ -- Apr 17

• Rename docker-new/ to docker/
• Drop -new suffixes from workflow filenames
• Update all references