Skip to content

Conversation

@austinvazquez
Copy link
Contributor

@austinvazquez austinvazquez commented Oct 20, 2025

github.com/docker/docker/pkg/progress

What I did

This changes copies the streamformatter and progress packages from github.com/docker/docker/api. The upcoming Docker 29 release is introducing Go modules: moby/api, moby/client, and moby/moby. Previously part of the top level pkg package, the streamformatter and progress packages are being made internal daemon packages.

Related issue

Moby issue: moby/moby#50575
Moby PR: moby/moby#51153

(not mandatory) A picture of a cute animal, if possible in relation to what you did

@austinvazquez austinvazquez force-pushed the refactor-moby-api-pkg-usage branch from 5d8c97e to ee3e2bd Compare October 21, 2025 01:14
@austinvazquez austinvazquez changed the title Refactor to remove dependencies on github.com/moby/moby/api/pkg/strea… Refactor to remove dependencies on github.com/docker/docker/pkg/streamformatter and Oct 21, 2025
@austinvazquez austinvazquez force-pushed the refactor-moby-api-pkg-usage branch from ee3e2bd to b3a3372 Compare October 21, 2025 01:24
@austinvazquez austinvazquez force-pushed the refactor-moby-api-pkg-usage branch from b3a3372 to 496ef8d Compare October 21, 2025 01:32
@austinvazquez austinvazquez marked this pull request as ready for review October 21, 2025 01:33
@austinvazquez austinvazquez requested a review from a team as a code owner October 21, 2025 01:33
Copy link
Contributor

@glours glours left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM + tests ok

@ndeloof
Copy link
Contributor

ndeloof commented Oct 21, 2025

Copied from https://github.com/moby/moby

Why?
We should just follow code being relocated in api module: moby/moby#50565

Copy link
Contributor

@ndeloof ndeloof left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't copy code inside compose but use new api module

@austinvazquez
Copy link
Contributor Author

Copied from https://github.com/moby/moby

Why? We should just follow code being relocated in api module: moby/moby#50565

👍🏼 , @ndeloof, I added a writeup to the description to clarify. PTAL.

@ndeloof
Copy link
Contributor

ndeloof commented Oct 21, 2025

is the docker/cli also supposed to use a local copy of this code then?
IMHO moby/moby#51153 is just wrong. /imageBuild API to render build events is non-trivial to manage and this deserves a utility package to handle rendering.

@austinvazquez
Copy link
Contributor Author

I have opened docker/cli#6570 but no review yet from CLI folks. IIUC yes there probably can be a shared place between CLI and compose. Just not sure where that needs to be.

@ndeloof
Copy link
Contributor

ndeloof commented Oct 21, 2025

I'm fine this code is relocated in docker/cli, I just wonder how it will be used if made internal in moby, as this is basically API-consumer code

@ndeloof
Copy link
Contributor

ndeloof commented Oct 21, 2025

we already have docker/cli as a dependency, so if it eventually own (a copy of) this code, would be simpler we just us it from there vs have our own copy

@austinvazquez
Copy link
Contributor Author

I've pushed a new revision to moby/moby#51153 to move the packages out of the api module up into the moby client. Probably long term we can investigate having these be in a better location perhaps CLI or some other Go SDK. For now this unblocks the API module release. Thanks!

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.

3 participants