Who is this for and what problem do they have today?
Operators who build or scan rpk currently inherit the deprecated
github.com/docker/docker Go module. Redpanda v26.1.13 pins
github.com/docker/docker v28.5.2+incompatible in src/go/rpk/go.mod.
Moby no longer updates that legacy module and directs Go consumers to
github.com/moby/moby/client and github.com/moby/moby/api.
What are the success criteria?
- Migrate rpk imports to the supported Moby client and API modules.
- Update go.mod and go.sum.
- Validate affected Docker client behavior through the rpk test suite.
- Document any minimum Docker API compatibility changes.
Why is solving this problem impactful?
This removes reliance on a deprecated dependency and allows downstream
users to consume maintained Docker client and API modules.
Additional notes
Moby v29 includes API changes, so this likely requires a source migration
rather than an in-place dependency bump.
Who is this for and what problem do they have today?
Operators who build or scan rpk currently inherit the deprecated
github.com/docker/docker Go module. Redpanda v26.1.13 pins
github.com/docker/docker v28.5.2+incompatible in src/go/rpk/go.mod.
Moby no longer updates that legacy module and directs Go consumers to
github.com/moby/moby/client and github.com/moby/moby/api.
What are the success criteria?
Why is solving this problem impactful?
This removes reliance on a deprecated dependency and allows downstream
users to consume maintained Docker client and API modules.
Additional notes
Moby v29 includes API changes, so this likely requires a source migration
rather than an in-place dependency bump.