chore(deps): Bump github.com/containerd/containerd from 1.4.3 to 1.4.4

[dependabot]

Bumps github.com/containerd/containerd from 1.4.3 to 1.4.4.

Release notes

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

containerd 1.4.4

Welcome to the v1.4.4 release of containerd!

The fourth patch release for containerd 1.4 contains a fix for CVE-2021-21334 along with various other minor issues. See GHSA-6g2q-w5j3-fwh4 for more details related to CVE-2021-21334.

Notable Updates

• Fix container create in CRI to prevent possible environment variable leak between containers #1628
• Update shim server to return grpc NotFound error #4872
• Add bounds on max oom_score_adj value for shim's AdjustOOMScore #4874
• Update task manager to use fresh context when calling shim shutdown #4929
• Update Docker resolver to avoid possible concurrent map access panic #4941
• Update shim's log file open flags to avoid containerd hang on syscall open #4971
• Fix incorrect usage calculation #5019

Please try out the release binaries and report any issues at https://github.com/containerd/containerd/issues.

Contributors

• Shengjing Zhu
• Derek McGowan
• Sebastiaan van Stijn
• Phil Estes
• Akihiro Suda
• Wei Fu
• Michael Crosby
• Mike Brown
• Phil Estes
• Tõnis Tiigi
• Danail Branekov
• IceberGu
• Maksym Pavlenko
• Simon Kaegi
• Zhiyu Li

Changes

• 05f951a37 Merge pull request from GHSA-6g2q-w5j3-fwh4
• 3ba4a3171 Prepare release notes for 1.4.4
• a22f1f642 Merge pull request #5107 from zhsj/update-cri
• cbcb2f57f vendor: update cri
• da919aa2a Merge pull request #5103 from AkihiroSuda/cache-vagrant-14
• 633bfb712 CI: cache ~/.vagrant.d/boxes
• 23495ab4a Merge pull request #5082 from AkihiroSuda/fix-5077-14
• e7851d743 CI: fix "ls: cannot access '/etc/cni/net.d': Permission denied"

... (truncated)

Changelog

Sourced from github.com/containerd/containerd's changelog.

Versioning and Release

This document details the versioning and release plan for containerd. Stability is a top goal for this project and we hope that this document and the processes it entails will help to achieve that. It covers the release process, versioning numbering, backporting, API stability and support horizons.

If you rely on containerd, it would be good to spend time understanding the areas of the API that are and are not supported and how they impact your project in the future.

This document will be considered a living document. Supported timelines, backport targets and API stability guarantees will be updated here as they change.

If there is something that you require or this document leaves out, please reach out by filing an issue.

Releases

Releases of containerd will be versioned using dotted triples, similar to Semantic Version. For the purposes of this document, we will refer to the respective components of this triple as <major>.<minor>.<patch>. The version number may have additional information, such as alpha, beta and release candidate qualifications. Such releases will be considered "pre-releases".

Major and Minor Releases

Major and minor releases of containerd will be made from master. Releases of containerd will be marked with GPG signed tags and announced at https://github.com/containerd/containerd/releases. The tag will be of the format v<major>.<minor>.<patch> and should be made with the command git tag -s v<major>.<minor>.<patch>.

After a minor release, a branch will be created, with the format release/<major>.<minor> from the minor tag. All further patch releases will be done from that branch. For example, once we release v1.0.0, a branch release/1.0 will be created from that tag. All future patch releases will be done against that branch.

Pre-releases

Pre-releases, such as alphas, betas and release candidates will be conducted from their source branch. For major and minor releases, these releases will be done from master. For patch releases, these pre-releases should be done within the corresponding release branch.

While pre-releases are done to assist in the stabilization process, no guarantees are provided.

... (truncated)

Commits

• 05f951a Merge pull request from GHSA-6g2q-w5j3-fwh4
• 3ba4a31 Prepare release notes for 1.4.4
• a22f1f6 Merge pull request #5107 from zhsj/update-cri
• cbcb2f5 vendor: update cri
• da919aa Merge pull request #5103 from AkihiroSuda/cache-vagrant-14
• 633bfb7 CI: cache ~/.vagrant.d/boxes
• 23495ab Merge pull request #5082 from AkihiroSuda/fix-5077-14
• e7851d7 CI: fix "ls: cannot access '/etc/cni/net.d': Permission denied"
• 8a7e41c Merge pull request #5018 from zhsj/bpo-4974
• 758f076 Merge pull request #5019 from zhsj/bpo-4808
• 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 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)

[dependabot]

Looks like github.com/containerd/containerd is up-to-date now, so this is no longer needed.