Skip to content

feat: describe image build, pull and push responses as progress streams - #3

Merged
mokevnin merged 1 commit into
mainfrom
feat/progress-streams
Sep 27, 2026
Merged

mokevnin merged 1 commit into
mainfrom
feat/progress-streams

Conversation

@mokevnin

Copy link
Copy Markdown
Member

ImageBuild, ImageCreate and ImagePush returned void, so the progress messages the Engine API streams back had no type. That includes the errorDetail line that ends a failed build with status 200. The official swagger documents only no error for these responses; the messages are its BuildInfo, CreateImageInfo and PushImageInfo definitions.

  • Operations: they return HttpStream<…, "application/json"> from @typespec/http/streams.
  • BuildInfo.aux: ImageID | string. The classic builder sends the image id; BuildKit sends a base64 protobuf StatusResponse when id is moby.buildkit.trace.
  • PushImageInfo.aux: {Tag, Digest, Size}.
  • Legacy fields: error and progress are #deprecated; the daemon still sends them.
  • Tooling: TypeSpec moves to 1.16, @typespec/streams is added.

The SDK side is Hexlet/docker-ruby#25.

🤖 Generated with Claude Code

The three operations returned void, so the progress messages the Engine API
streams back, including the error that ends a failed build, had no type.
They now return HttpStream of BuildInfo, CreateImageInfo and PushImageInfo,
whose aux carries what each daemon sends: an image id, a BuildKit trace or
the pushed digest. TypeSpec moves to 1.16 for @typespec/streams.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mokevnin
mokevnin merged commit 1ff9127 into main Sep 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant