Bump github.com/docker/docker from 25.0.5+incompatible to 25.0.6+incompatible

[dependabot]

Bumps github.com/docker/docker from 25.0.5+incompatible to 25.0.6+incompatible.

Release notes

Sourced from github.com/docker/docker's releases.

v25.0.6

25.0.6

For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones:

• docker/cli, 25.0.6 milestone
• moby/moby, 25.0.6 milestone
• Deprecated and removed features, see Deprecated Features.
• Changes to the Engine API, see API version history.

Security

This release contains a fix for CVE-2024-41110 / GHSA-v23v-6jw2-98fq that impacted setups using authorization plugins (AuthZ) for access control.

Bug fixes and enhancements

• [25.0] remove erroneous platform from image config OCI descriptor in docker save output. moby/moby#47695
• [25.0 backport] Fix a nil dereference when getting image history for images having layers without the Created value set. moby/moby#47759
• [25.0 backport] apparmor: Allow confined runc to kill containers. moby/moby#47830
• [25.0 backport] Fix an issue where rapidly promoting a Swarm node after another node was demoted could cause the promoted node to fail its promotion. moby/moby#47869
• [25.0 backport] don't depend on containerd platform.Parse to return a typed error. moby/moby#47890
• [25.0 backport] builder/mobyexporter: Add missing nil check moby/moby#47987

Packaging updates

• Update AWS SDK Go v2 to v1.24.1 for AWS CloudWatch logging driver. moby/moby#47724
• Update Go runtime to 1.21.12, which contains security fixes for CVE-2024-24791 moby/moby#48146
• Update Containerd (static binaries only) to v1.7.20. moby/moby#48199

Full Changelog: moby/moby@v25.0.5...v25.0.6

Commits

• b08a51f Merge pull request #48231 from austinvazquez/backport-vendor-otel-v0.46.1-to-...
• d151b0f vendor: OTEL v0.46.1 / v1.21.0
• c6ba9a5 Merge pull request #48225 from austinvazquez/backport-workflow-artifact-reten...
• 4673a3c Merge pull request #48227 from austinvazquez/backport-backport-branch-check-t...
• 30f8908 github/ci: Check if backport is opened against the expected branch
• 7454d6a ci: update workflow artifacts retention
• 65cc597 Merge commit from fork
• b722836 Merge pull request #48199 from austinvazquez/update-containerd-binary-to-1.7.20
• e8ecb9c update containerd binary to v1.7.20
• e6cae1f update containerd binary to v1.7.19
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[mkjpryor]

Hopefully this can merge and be released quickly, because the existence of a critical CVE in Helm is currently breaking our builds.

[mkjpryor]

@mattfarina

Don't mean to nag, but any chance this can get merged and into a patch release ASAP? The CVE has been open for nearly two weeks and is blocking a lot of people.

[scottrigby]

This was a false positive. Helm does not use the affected functionality in docker engine. This is an indirect dependency of ORAS v1, which Helm registry package only uses to pull images. However merging this to help reduce noise from others importing Helm.

This can be evidenced with govulncheck:

$ git switch --detach v3.15.3
$ govulncheck ./...
Scanning your code and 961 packages across 149 dependent modules for known vulnerabilities...
=== Symbol Results ===
No vulnerabilities found.
Your code is affected by 0 vulnerabilities.
This scan also found 0 vulnerabilities in packages you import and 1
vulnerability in modules you require, but your code doesn't appear to call these
vulnerabilities.
Use '-show verbose' for more details.

It would be helpful and appreciated to work with your vendor(s) to reduce these false positives. They cause a lot of noise (for everyone).

For this specific version bump. Since this not an actual issue, it will go into the next patch release (v3.15.4), scheduled for next Wednesday (see the "Release Calendar" on https://helm.sh/).