chore(deps): bump github.com/docker/docker from 1.4.2-0.20200203170920-46ec8731fbce to 20.10.27+incompatible

[dependabot[bot]]

Bumps github.com/docker/docker from 1.4.2-0.20200203170920-46ec8731fbce 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

• See full diff 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.

[jenkins-x-bot]

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

I'm waiting for a jenkins-x 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. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[jenkins-x-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: To complete the pull request process, please assign tomhobson You can assign the PR to them by writing /assign @tomhobson in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment