fix: the agent image build reads its Dockerfile from the context #12

Merged

morten-olsen merged 4 commits from mc/d50e173f-a8c1-46a2-889f-e1c5b7e1bcc5 into main 2026-10-07 15:58:09 +02:00

Conversation 0 Commits 4 Files changed 3 +7 -7

paperclip commented 2026-10-07 15:54:26 +02:00

Contributor

• Copy link
• Copy Markdown

Summary

Release v0.6.0 (pipeline 65): image-agent built the executable (32s) but publish failed in 4s with Kaniko's error resolving dockerfile path: please provide a valid path to a Dockerfile within the build context with --dockerfile. The scan step did not run. The second workflow of that tag (release, binaries) is separate.

Probable cause: the setting dockerfile: ${CI_WORKSPACE}/docker/agent/Dockerfile did not resolve to a real file (I assumed Woodpecker substitutes CI_WORKSPACE in settings; the failure suggests it does not, or Kaniko wants the file inside the context). I could not reproduce Kaniko here, so this is a hypothesis.

Fix without relying on it: task release:agent-context copies docker/agent/Dockerfile into dist/release beside the executable, and the workflow drops the dockerfile setting, so the plugin's default Dockerfile in the context (dist/release) is used. task image:agent is unchanged (it uses --file).

Evidence

• Error from Morten's paste of pipeline 65; the executable step succeeded, so the context and executable are fine.
• woodpecker-cli lint --strict .woodpecker valid; prettier clean. Not run: Kaniko. The context: dist/release is still relative, which the plugin passes through as --context; if the next run fails on that, the fix is the same pattern with an absolute path from a shell step.

Merge danger

Config only; the workflow runs on tags only. Needs a new release after merging (the failed v0.6.0 tag keeps its old config).

Rollback

Revert the commit.

After rollout

New tag: image-agent publish and scan succeed, then ai/mission-control-agent:<version> exists.

## Summary Release v0.6.0 (pipeline 65): `image-agent` built the executable (32s) but `publish` failed in 4s with Kaniko's `error resolving dockerfile path: please provide a valid path to a Dockerfile within the build context with --dockerfile`. The `scan` step did not run. The second workflow of that tag (`release`, binaries) is separate. Probable cause: the setting `dockerfile: ${CI_WORKSPACE}/docker/agent/Dockerfile` did not resolve to a real file (I assumed Woodpecker substitutes `CI_WORKSPACE` in settings; the failure suggests it does not, or Kaniko wants the file inside the context). I could not reproduce Kaniko here, so this is a hypothesis. Fix without relying on it: `task release:agent-context` copies `docker/agent/Dockerfile` into `dist/release` beside the executable, and the workflow drops the `dockerfile` setting, so the plugin's default `Dockerfile` in the context (`dist/release`) is used. `task image:agent` is unchanged (it uses `--file`). ## Evidence - Error from Morten's paste of pipeline 65; the `executable` step succeeded, so the context and executable are fine. - `woodpecker-cli lint --strict .woodpecker` valid; prettier clean. Not run: Kaniko. The `context: dist/release` is still relative, which the plugin passes through as `--context`; if the next run fails on that, the fix is the same pattern with an absolute path from a shell step. ## Merge danger Config only; the workflow runs on tags only. Needs a new release after merging (the failed v0.6.0 tag keeps its old config). ## Rollback Revert the commit. ## After rollout New tag: `image-agent` publish and scan succeed, then `ai/mission-control-agent:<version>` exists.

paperclip added 4 commits 2026-10-07 15:54:26 +02:00

feat: a release tag also builds the agent image, both images are scanned and their base pinned ... c99f73a4d0

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

fix: quote the scan steps' image so an empty tag does not break the YAML of every pipeline ... e26b09be77

On a push the unquoted ${CI_COMMIT_TAG##v} expands to nothing and leaves 'agent:' as a mapping
key, so Woodpecker rejected the whole repo's config (pipelines 57-60 errored).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

Merge remote-tracking branch 'origin/mc/d50e173f-a8c1-46a2-889f-e1c5b7e1bcc5' into mc/d50e173f-a8c1-46a2-889f-e1c5b7e1bcc5 6436e832cc

fix: the agent image build reads its Dockerfile from the context ... 188d020570

Kaniko failed on v0.6.0 with 'error resolving dockerfile path'. The Dockerfile is copied beside
the executable in dist/release, so the plugin's default Dockerfile path is the right one.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

morten-olsen merged commit 244eb47d6f into main 2026-10-07 15:58:09 +02:00

morten-olsen deleted branch mc/d50e173f-a8c1-46a2-889f-e1c5b7e1bcc5 2026-10-07 15:58:09 +02:00

morten-olsen referenced this pull request from a commit 2026-10-07 15:58:10 +02:00

fix: the agent image build reads its Dockerfile from the context (#12)

paperclip referenced this pull request 2026-10-07 16:06:02 +02:00

fix: the agent image builds under Kaniko, and a release tag builds the server image #14

morten-olsen referenced this pull request from a commit 2026-10-07 16:06:54 +02:00

fix: the agent image builds under Kaniko, and a release tag builds the server image (#14)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

ai/mission-control!12

No description provided.