Bump github.com/docker/docker from 20.10.22+incompatible to 20.10.24+incompatible

[dependabot[bot]]

Bumps github.com/docker/docker from 20.10.22+incompatible to 20.10.24+incompatible.

Release notes

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

v20.10.24

20.10.24

Bug fixes and enhancements

• Fixed a number of issues that can cause Swarm encrypted overlay networks to fail to uphold their guarantees, addressing CVE-2023-28841, CVE-2023-28840, and CVE-2023-28842.
  • A lack of kernel support for encrypted overlay networks now reports as an error.
  • Encrypted overlay networks are eagerly set up, rather than waiting for multiple nodes to attach.
  • Encrypted overlay networks are now usable on Red Hat Enterprise Linux 9 through the use of the xt_bpf kernel module.
  • Users of Swarm overlay networks should review GHSA-vwm3-crmr-xfxw to ensure that unintentional exposure has not occurred.
• Upgrade github.com/containerd/fifo to v1.1.0 to fix a potential panic moby/moby#45216.
• Fix missing Bash completion for installed cli-plugins docker/cli#4091.

Packaging Updates

• Update Go runtime to 1.19.7.
• Update Docker Buildx to v0.10.4.
• Update containerd to v1.6.20.
• Update runc to v1.1.5.

v20.10.23

Bug fixes and enhancements

• Fix an issue where docker build would fail when using --add-host=host.docker.internal:host-gateway with BuildKit enabled moby/moby#44650.

• Revert seccomp: block socket calls to AF_VSOCK in default profile moby/moby#44712. This change, while favorable from a security standpoint, caused a change in behavior for some use-cases. As such, we are reverting it to ensure stability and compatibility for the affected users.

  However, users of AF_VSOCK in containers should recognize that this (special) address family is not currently namespaced in any version of the Linux kernel, and may result in unexpected behavior, like containers communicating directly with host hypervisors.

  Future releases, will filter AF_VSOCK. Users who need to allow containers to communicate over the unnamespaced AF_VSOCK will need to turn off seccomp confinement or set a custom seccomp profile.

Packaging Updates

• Update Docker Compose to v2.15.1.

... (truncated)

Commits

• 5d6db84 Merge pull request from GHSA-232p-vwff-86mp
• d2bc43a Merge pull request #45242 from neersighted/go1.19.7/20.10
• 9aa5d55 update to go1.19.7
• 83679bb Merge pull request #45216 from corhere/backport-20.10/containerd-fifo_v1.1
• b4f0442 Merge pull request #45219 from vvoland/test-windows-execstartfails-2010
• ba043e8 Merge pull request #44990 from thaJeztah/20.10_backport_update_go1.19
• b56fe59 integration-cli: Enable TestExecStartFails on Windows
• d9433ee Merge pull request #45197 from vvoland/integration-restart-race-2010
• a9c02c2 Upgrade containerd/fifo to v1.1.0
• bbec670 [20.10] vendor: libnetwork c5aa85f9b25f0acaec8591ced679cb9fb5b9e32c
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 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](https://github.com/tektoncd/results/network/alerts).

> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[tekton-robot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[khrm]

/release-note-none

[adambkaplan]

I'd like to do a depedency graph analysis - pulling in docker/docker feels very unnecessary and should be removed if possible.

[khrm]

Yes, these docker dependencies are being pulled indirectly. I can see that tekton/pipelines also have docker dependencies indirectly.

[khrm]

@dependabot rebase

[khrm]

We have alert https://github.com/tektoncd/results/security/dependabot?q=package%3Agithub.com%2Fdocker%2Fdocker+manifest%3Ago.mod+has%3Apatch for this docker dependency.

[linux-foundation-easycla[bot]]

The committers listed above are authorized under a signed CLA.

• :white_check_mark: login: dependabot[bot] (5c02b63d3d6885f51833df9a2a0b59d24487340a)

[khrm]

/easy-cla

[tekton-robot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale with a justification. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[khrm]

@dependabot rebase

[khrm]

@dependabot reopen

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: khrm

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/tektoncd/results/blob/main/OWNERS)~~ [khrm] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment