mirror of
https://github.com/azaion/gps-denied-onboard.git
synced 2026-06-22 17:21:13 +00:00
Oleksandr Bezdieniezhnykh
1f634c2604
ci/woodpecker/push/02-build-push Pipeline failed
- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests. - Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps. - Updated architectural documentation to include the new demo replay operator flow and its dependencies. - Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation. - Added new entries in the dependencies table for upcoming tasks related to the demo replay flow. These changes improve clarity and usability for operators and developers working with the demo replay system.
50 lines
2.2 KiB
Markdown
50 lines
2.2 KiB
Markdown
# Step 2: Containerization
|
|
|
|
**Role**: DevOps / Platform engineer
|
|
**Goal**: Define Docker configuration for every component, local development, and blackbox test environments.
|
|
**Constraints**: Plan only — no Dockerfile creation. Describe what each Dockerfile should contain.
|
|
|
|
## Steps
|
|
|
|
1. Read `architecture.md` and all component specs
|
|
2. Read `restrictions.md` for infrastructure constraints
|
|
3. Research best Docker practices for the project's tech stack (multi-stage builds, base image selection, layer optimization)
|
|
4. For each component, define:
|
|
- Base image (pinned version, prefer alpine/distroless for production)
|
|
- Build stages (dependency install, build, production)
|
|
- Non-root user configuration
|
|
- Health check endpoint and command
|
|
- Exposed ports
|
|
- `.dockerignore` contents
|
|
5. Define `docker-compose.yml` for local development:
|
|
- All application components
|
|
- Database (Postgres) with named volume
|
|
- Any message queues, caches, or external service mocks
|
|
- Shared network
|
|
- Environment variable files (`.env`)
|
|
6. Define `docker-compose.test.yml` for blackbox tests:
|
|
- Application components under test
|
|
- Test runner container (black-box, no internal imports)
|
|
- Isolated database with seed data
|
|
- All tests runnable via `docker compose -f docker-compose.test.yml up --abort-on-container-exit --exit-code-from e2e-runner`
|
|
- See the Woodpecker two-workflow contract in [`../templates/ci_cd_pipeline.md`](../templates/ci_cd_pipeline.md) — the test runner entry point defined here becomes the first step of `.woodpecker/01-test.yml`.
|
|
7. Define image tagging strategy: `<registry>/<project>/<component>:<git-sha>` for CI, `latest` for local dev only
|
|
|
|
## Self-verification
|
|
|
|
- [ ] Every component has a Dockerfile specification
|
|
- [ ] Multi-stage builds specified for all production images
|
|
- [ ] Non-root user for all containers
|
|
- [ ] Health checks defined for every service
|
|
- [ ] `docker-compose.yml` covers all components + dependencies
|
|
- [ ] `docker-compose.test.yml` enables black-box testing
|
|
- [ ] `.dockerignore` defined
|
|
|
|
## Save action
|
|
|
|
Write `containerization.md` using `templates/containerization.md`.
|
|
|
|
## Blocking
|
|
|
|
**BLOCKING**: Present containerization plan to user. Do NOT proceed until confirmed.
|