Sourced fromgithub.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 networksto fail to uphold their guarantees, addressingCVE-2023-28841,CVE-2023-28840, andCVE-2023-28842.
  • A lack of kernel support for encrypted overlay networks now reportsas an error.
  • Encrypted overlay networks are eagerly set up, rather than waiting formultiple nodes to attach.
  • Encrypted overlay networks are now usable on Red Hat Enterprise Linux 9through the use of thext_bpf kernel module.
  • Users of Swarm overlay networks should reviewGHSA-vwm3-crmr-xfxwto ensure that unintentional exposure has not occurred.
• Upgrade github.com/containerd/fifo to v1.1.0 to fix a potential panicmoby/moby#45216.
• Fix missing Bash completion for installed cli-pluginsdocker/cli#4091.

Packaging Updates

• Update Go runtime to1.19.7.
• Update Docker Buildx tov0.10.4.
• Update containerd tov1.6.20.
• Update runc tov1.1.5.

v20.10.23

Bug fixes and enhancements

• Fix an issue wheredocker build would fail when using--add-host=host.docker.internal:host-gatewaywith BuildKit enabledmoby/moby#44650.

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

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

  Future releases, will filterAF_VSOCK. Users who need to allow containersto communicate over the unnamespacedAF_VSOCK will need to turn off seccompconfinement or set a custom seccomp profile.

Packaging Updates

• Update Docker Compose tov2.15.1.

... (truncated)

• 5d6db84 Merge pull request fromGHSA-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 incompare view

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 theSecurity Alerts page.