chore(deps): bump github.com/docker/docker from 20.10.7+incompatible to 20.10.27+incompatible in /tests

[dependabot]

Bumps github.com/docker/docker from 20.10.7+incompatible to 20.10.27+incompatible.

Release notes

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

v20.10.27

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

• docker/cli, 20.10.27 milestone
• moby/moby, 20.10.27 milestone

Bug Fixes and Enhancements

• Fix dockerd-rootless-setuptools.sh when user name contains a backslash. moby/moby#46424
• Add IP_NF_MANGLE to check-config.sh to the "generally required" list in check-config.sh because it is required by Swarm. moby/moby#46674
• Fix a deadlock in libnetwork which could prevent containers from starting. moby/moby#46693
• Write overlay2 layer metadata atomically. moby/moby#46705
• Support building with Go 1.20. moby/moby#46694 moby/moby#46695 moby/moby#46696

Packaging Updates

• Update to go1.20.10, golang/org/x/net v0.17.0. moby/moby#46692

Security

• Deny containers access to /sys/devices/virtual/powercap by default. This change hardens against CVE-2020-8694, CVE-2020-8695, and CVE-2020-12912, and an attack known as the PLATYPUS attack. For more details, see advisory, commit.

v20.10.26

20.10.26

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

• docker/cli, 20.10.26 milestone
• moby/moby, 20.10.26 milestone

Bug Fixes and Enhancements

• Support filesystems which do not support extended file attributes with the VFS graph driver. moby/moby#45466
• Fix AppArmor profile docker-default /proc/sys rule. moby/moby#45716
• seccomp: always allow name_to_handle_at(2). moby/moby#45835
• Fix an issue which prevented volumes mounted to a live-restored container from being removed. moby/moby#45840
• client: resolve an incompatibility with Go 1.20.6, Go 1.20.7, Go 1.19.11 and Go 1.19.12. moby/moby#45972
• windows: fix --register-service when executed from within binary directory. moby/moby#46217

Packaging Updates

• Update Go to 1.19.12. moby/moby#46142
• Update containerd to v1.6.22. moby/moby#46105
• Update runc to v1.1.8. moby/moby#46031
• Delete Upstart init scripts and clean up sysvinit. moby/moby#46047

v20.10.25

Bug fixes and enhancements

• Fix log loss with the AWSLogs log driver moby/moby#45349

... (truncated)

Commits

• 81ebe71 Merge pull request from GHSA-jq35-85cj-fj4p
• fb63665 Merge pull request #46705 from thaJeztah/20.10_backport_atomic-layer-data-write
• b967d89 Merge pull request #46692 from corhere/backport-20.10/update-x-net-v0.17
• 2c22bd5 vendor: golang.org/x/net v0.17.0
• d862c21 Update to go1.20.10
• cb47414 Merge pull request #46696 from corhere/backport-20.10/go1.20-enablement
• ea4eb73 Merge pull request #46695 from corhere/backport-20.10/safer-fileinfo
• 6c523aa hack: fix suppressing Xattrs lint errors
• 31b8374 pkg/archive: audit gosec file-traversal lints
• 8e44855 Remove local fork of archive/tar package
• 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.

[pull-request-quantifier-deprecated]

This PR has 6 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +3 -3
Percentile : 2.4%

Total files changed: 2

Change summary by file extension:
.mod : +1 -1
.sum : +2 -2

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.