deps: bump the moby group with 2 updates

[dependabot]

Bumps the moby group with 2 updates: github.com/moby/moby/api and github.com/moby/moby/client.

Updates github.com/moby/moby/api from 1.55.0 to 1.56.0

Release notes

Sourced from github.com/moby/moby/api's releases.

api/v1.56.0

1.56.0

Changelog

• GET /containers/json now supports an annotation filter to filter containers by annotation, either by key (annotation=key) or by key and value (annotation="key=value"), similar to the existing label filter. moby/moby#53538
• POST /containers/create now supports HostConfig.Umask to set the initial umask for a Unix container. When set, the daemon includes the value in the OCI process configuration for the container's entrypoint, exec processes, and healthchecks. When omitted, the runtime's default behavior applies.moby/moby#53463
• api/docs: sync API docs v1.25 - v1.55. moby/moby#53246
• api/swagger: Align Healthcheck name with Go struct. moby/moby#53567
• api/types/plugin: Deprecated plugin.Privileges sorting methods in favor of slices.SortFunc. moby/moby#53511
• api/types/plugin: fix Privileges Swap implementation. moby/moby#53510
• api: Bump to 1.56. moby/moby#53425
• api: document Task.NetworksAttachments in the swagger definition. moby/moby#53082
• api: remove gotest.tools from tests. moby/moby#53535
• api: swagger: Use int64 for build query params. moby/moby#53520
• api: use blackbox testing. moby/moby#53525
• Fix API reference documenting an unsupported names filter for GET /configs. moby/moby#53447

Commits

• 9b2179d Merge pull request #53572 from vvoland/api-docs-cut
• 575cf82 Merge pull request #53571 from thaJeztah/bump_tools
• 20beedb api/docs: Cut v1.56
• bb86302 Merge pull request #53569 from vvoland/afvsock-lsm
• 65be55a Merge pull request #53513 from thaJeztah/daemon_fix_list
• 0af79c4 Merge pull request #53570 from vvoland/process-release
• 7d1ce6a Merge pull request #53568 from renovate-bot/renovate/github.com-mdlayher-sock...
• 0df1a00 Dockerfile: update cli v29.7.2, compose v5.5.1, buildx v0.37.0
• e1d06bd Drop replace rules
• b40d37e Merge pull request #53359 from vvoland/ext-namegenerator
• Additional commits viewable in compare view

Updates github.com/moby/moby/client from 0.5.1 to 0.6.0

Release notes

Sourced from github.com/moby/moby/client's releases.

client/v0.6.0

0.6.0

Changelog

• pkg/jsonmessage: add new WithMessagePrinter option to use a custom printer for messages. moby/moby#53489
• api: Bump to 1.56. moby/moby#53425
• minor cleanups, refactors. moby/moby#53509

Changelog

Sourced from github.com/moby/moby/client's changelog.

0.6.0 (2013-08-22)

• Runtime: Load authConfig only when needed and fix useless WARNING

• Runtime: Add lxc-conf flag to allow custom lxc options

• Runtime: Fix race conditions in parallel pull
• Runtime: Improve CMD, ENTRYPOINT, and attach docs.

• Documentation: Small fix to docs regarding adding docker groups
• Documentation: Add MongoDB image example

• Builder: Add USER instruction do Dockerfile

• Documentation: updated default -H docs
• Remote API: Sort Images by most recent creation date.

• Builder: Add workdir support for the Buildfile
• Runtime: Add an option to set the working directory

• Runtime: Show tag used when image is missing

• Documentation: Update readme with dependencies for building
• Documentation: Add instructions for creating and using the docker group
• Remote API: Reworking opaque requests in registry module

• Runtime: Fix Graph ByParent() to generate list of child images per parent image.

• Runtime: Add Image name to LogEvent tests
• Documentation: Add sudo to examples and installation to documentation

• Hack: Bash Completion: Limit commands to containers of a relevant state

• Remote API: Add image name in /events
• Runtime: Apply volumes-from before creating volumes

• Runtime: Make docker run handle SIGINT/SIGTERM
• Runtime: Prevent crash when .dockercfg not readable

• Hack: Add docker dependencies coverage testing into docker-ci

• Runtime: Add -privileged flag and relevant tests, docs, and examples
• Packaging: Docker-brew 0.5.2 support and memory footprint reduction

• Runtime: Install script should be fetched over https, not http.

• Packaging: Add new docker dependencies into docker-ci
• Runtime: Use Go 1.1.2 for dockerbuilder
• Registry: Improve auth push
• Runtime: API, issue 1471: Use groups for socket permissions
• Documentation: PostgreSQL service example in documentation
• Contrib: bash completion script
• Tests: Improve TestKillDifferentUser to prevent timeout on buildbot
• Documentation: Fix typo in docs for docker run -dns
• Documentation: Adding a reference to ps -a

• Runtime: Correctly detect IPv4 forwarding
• Packaging: Revert "docker.upstart: avoid spawning a sh process"

• Runtime: Use ranged for loop on channels

• Runtime: Fix typo: fmt.Sprint -> fmt.Sprintf
• Tests: Fix typo in TestBindMounts (runContainer called without image)

• Runtime: add websocket support to /container//attach/ws
• Runtime: Mount /dev/shm as a tmpfs

• Builder: Only count known instructions as build steps
• Builder: Fix docker build and docker events output
• Runtime: switch from http to https for get.docker.io

• Tests: Improve TestGetContainersTop so it does not rely on sleep

• Packaging: Docker-brew and Docker standard library

• Testing: Add some tests in server and utils

... (truncated)

Commits

• f4a4f1c Bump to 0.6.0
• f925edd Merge pull request #1525 from griff/1503-fix
• 12715c8 Merge pull request #1609 from jpetazzo/release-docker-with-docker
• 326dadd Merge pull request #1565 from dotcloud/only_load_authconfig_when_needed
• a3510c9 Merge pull request #1560 from dotcloud/439-allow-lxc-args
• 262d57e Merge pull request #1623 from mhennings/1592-fix-race-conditions-in-parallel-...
• 551092f Add lxc-conf flag to allow custom lxc options
• 3f802f4 Fix race conditions in parallel pull
• 0b9c8e2 Merge pull request #1596 from metalivedev/1149-easyfixes
• 42fe550 Merge pull request #1614 from denibertovic/docs
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dap-code-review-by-crunchloop]

Code Review — da4f040 · CLEAN

Clean review: no findings. This is a Dependabot group bump of moby/moby/api v1.55.0→v1.56.0 and moby/moby/client v0.5.1→v0.6.0 with no code change, and I found no incompatibility with any call site.

What I reviewed

What I verified, by reading the module sources of both versions (downloaded into the module cache; nothing built or executed):

• api diff — diff -rq of api@v1.55.0 vs api@v1.56.0 shows only docs, swagger, Dockerfile, go.mod/go.sum, and test files changed. No Go type in any package this repo imports (container, mount, network, build) changed.
• client diff — no exported signature or type was removed or changed. The only exported changes are the MaxAPIVersion const (1.55→1.56, the point of the bump) and a new additive WithMessagePrinter option. Everything else is unexported internals: the sendRequest/post/buildRequest family reordered body/headers arguments (unreachable from outside the package), a valueOrZero helper preserving ContainerUpdate semantics, and capability normalization moved from an in-place mutation of the caller's HostConfig to a non-mutating shallow copy in normalizeHostConfig — semantically identical normalization, and strictly better for callers.
• Version pairing — client v0.6.0's go.mod requires api v1.56.0, matching the bump; the dropped intra-monorepo replace directive was never applicable downstream. go mod download resolved both modules cleanly against the PR's go.mod/go.sum.
• Call sites — I enumerated every client.* symbol this repo uses (client.New, FromEnv, WithHost, Ping, the container/exec/image/network/volume option types and methods across runtime/docker/) and each still exists with the same shape. The version-negotiation comment in runtime/docker/client.go:35 remains accurate.

Coverage account: I worked interface-contract and correctness (the only dimensions a dependency-only bump can fire under in this repo) and verified the compat surface as above; the conditional dimensions (state-integrity, redelivery, version-compatibility on this repo's own persisted shapes, etc.) have no condition met by a two-line go.mod diff. I reviewed the diff at head da4f040 (1 commit, 2 files). The repository publishes no .dap/code-review.yml; its standard lives in .dap/review/engineering.md, which I read at the base SHA — its out-of-bounds rule for dependency bumps ("beyond an actual incompatibility you can point at in the diff") is satisfied since none exists. I did not run the build or test suite; a go build ./... run by CI would confirm compilation, but source reading found nothing that could break it.

---

_{CLEAN — this round found nothing. Reply in a finding's own thread to argue it. On the pull request I answer @dap-code-review-by-crunchloop review, pause and resume.}

[dap-code-review-by-crunchloop]

No open findings on da4f040.

_{The DAP Code Review check run remains the verdict of record. This approval is dismissed if a finding reopens or a later head is not clean.}