Files
tom_analysis_agent/.agents/plans/iter-02-platform-deployment/steps/step-1.md

2.2 KiB

Step 1: the image (E7)

Built 2026-10-20.

What was built

  • Dockerfile. Two stages. The builder installs the Execution engine from a named build context, engine, copying only its pyproject.toml and execution_engine/. The runtime stage holds app/, agents/, providers/ and skills/ in /app and runs python -m app.main as a non-root user (10001) on port 8080. The agent is not installed: ROOT in workflow.py is found from __file__, so it must run from its own folder, as the reference agent does.
  • Defaults for a container: CHECKPOINTER=sqlite with its files in the /data volume, and ENV_FILE_EXPORT=false.
  • .dockerignore: keeps .venv, .cache, .env, eval/results, deliverables, tests and plans out of the image.
podman build --build-context engine=../orchestration_engine -t localhost/agents/tom-analysis:local .

What differed from the plan

  • Credentials and the non-root user. The application default credentials file is mode 600, so the image's user cannot read it under rootless podman. The container is run with --userns=keep-id:uid=10001,gid=10001, which maps the developer's user onto the image's. The file's mode is not changed.
  • Podman ignores HEALTHCHECK in an OCI-format build. The compose entry declares its own (step 3).

Verified

  • Neither repository has a commit yet, so "a clean checkout" was taken as the files git would commit (git ls-files --cached --others --exclude-standard) of both, copied to an empty folder. The image built from that, and the Workflow loads in it with its five Phases.
  • The container answers /health and both agent card paths; the card advertises A2A_PUBLIC_URL. From inside it, the credentials are readable and a Gemini request on Vertex AI answers.
  • An A2A message/send with pre_approved, customer_case and scope in the message metadata reached the engine, which checked the spec. A Customer case that differs from the spec's is refused by name.
  • 177 tests pass; ruff and mypy are clean. No Python changed.

Not done

  • CI's means, a dependency on the engine's repository at a pinned commit, needs the engine's repository to have a commit to pin.