Skip to content

fix: align ambient-runner Dockerfile build context with other components#1260

Merged
mergify[bot] merged 2 commits intomainfrom
fix/runner-dockerfile-build-context
Apr 9, 2026
Merged

fix: align ambient-runner Dockerfile build context with other components#1260
mergify[bot] merged 2 commits intomainfrom
fix/runner-dockerfile-build-context

Conversation

@ambient-code
Copy link
Copy Markdown
Contributor

@ambient-code ambient-code bot commented Apr 9, 2026

Summary

  • Change COPY ambient-runner /app/ambient-runner to COPY . /app/ambient-runner so the build context matches the Dockerfile's directory (consistent with all other components)
  • Update context in components-build-deploy.yml, prod-release-deploy.yaml, e2e.yml, and claude-live-test.yml from ./components/runners to ./components/runners/ambient-runner
  • Update Makefile build-runner target to cd into the correct directory and drop the -f flag

Test plan

  • Verify make build-runner succeeds locally
  • Verify CI image build passes for ambient-runner
  • Verify E2E tests pass with updated build context
  • Confirm Konflux-style builds (context = Dockerfile parent) no longer error on the COPY instruction

Closes #1259


🤖 Ambient Session

Change the COPY instruction from `COPY ambient-runner ...` to `COPY . ...`
so the build context can be the Dockerfile's own directory, matching the
convention used by every other component. Update the GitHub Actions
workflows and Makefile accordingly.

Closes #1259

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ambient-code ambient-code bot added the ambient-code:managed PR managed by AI automation label Apr 9, 2026
@ambient-code
Copy link
Copy Markdown
Contributor Author

ambient-code bot commented Apr 9, 2026

This aligns the ambient-runner build context with the convention used by all other components:

Before: Build context = ./components/runners, Dockerfile uses COPY ambient-runner ...
After: Build context = ./components/runners/ambient-runner, Dockerfile uses COPY . ...

Files changed:

  • components/runners/ambient-runner/DockerfileCOPY . /app/ambient-runner
  • .github/workflows/components-build-deploy.yml — context updated
  • .github/workflows/prod-release-deploy.yaml — context updated
  • Makefilebuild-runner target updated

🤖 Session

…workflows

Missed these two workflows in the initial fix — they also hardcoded
the build context as `components/runners` instead of
`components/runners/ambient-runner`.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@mergify mergify bot added the queued label Apr 9, 2026
@mergify
Copy link
Copy Markdown

mergify bot commented Apr 9, 2026

Merge Queue Status

  • Entered queue2026-04-09 15:51 UTC · Rule: default
  • Checks skipped · PR is already up-to-date
  • Merged2026-04-09 15:52 UTC · at 48a2c88dde78ba6329bc9a09c1d77178592bd57e

This pull request spent 21 seconds in the queue, including 5 seconds running CI.

Required conditions to merge

@mergify mergify bot merged commit d5555f7 into main Apr 9, 2026
43 of 45 checks passed
@mergify mergify bot deleted the fix/runner-dockerfile-build-context branch April 9, 2026 15:52
@mergify mergify bot removed the queued label Apr 9, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 9, 2026

⚠️ SDD Preflight — Managed Paths Modified

This PR modifies files in SDD-managed component(s). These components are migrating to Spec-Driven Development.

File Component Mode
components/runners/ambient-runner/Dockerfile runner warn

No action required — these components are in warn mode. Consider using the component's agent workflow for future changes.

📖 Specs: Runner Spec · Runner Constitution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ambient-code:managed PR managed by AI automation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ambient-runner Dockerfile requires non-standard build context

1 participant