Skip to content

fix(cli): first run blockers for build - #445

Merged
savme merged 10 commits into
mainfrom
fix/build-first-run-blockers
Oct 7, 2026
Merged

savme merged 10 commits into
mainfrom
fix/build-first-run-blockers

Conversation

@savme

@savme savme commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

This PR fixes several UX issues and improves error reporting in datumctl compute build.

  • buildkit is now found using the same logic the docker CLI uses
  • push and build inspect read registry credentials the same way docker push does
  • build inspect can read the .tar files and folders that build --output saves
  • a Kraftfile-based build is only triggered when requested explicitly with --kraftfile
  • building the same input twice gives the same digest
  • saving to the same --output folder twice now works
  • problems with --output and --push are reported before the build starts

Fixes #240

@savme
savme requested a review from a team as a code owner October 6, 2026 16:29
@savme
savme merged commit 967cba7 into main Oct 7, 2026
11 of 12 checks passed
@savme
savme deleted the fix/build-first-run-blockers branch October 7, 2026 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

datumctl compute build has multiple first-run blockers: BuildKit connectivity, registry auth, and inspect

2 participants