Bump github.com/containerd/containerd from 1.6.0 to 1.6.1

[dependabot[bot]]

Bumps github.com/containerd/containerd from 1.6.0 to 1.6.1.

Release notes

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

containerd 1.6.1

Welcome to the v1.6.1 release of containerd!

The first patch release for containerd 1.6 includes a fix for CVE-2022-23648 and other issues.

Notable Updates

• Use fs.RootPath when mounting volumes (GHSA-crp2-qrr5-8pq7)
• Return init pid when clean dead shim in runc.v1/v2 shims (#6572)

See the changelog for complete list of changes

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

Contributors

• Derek McGowan
• Jeff Zvier
• Maksym Pavlenko
• Wei Fu
• ruiwen-zhao

Changes

• [release/1.6] Prepare release notes for v1.6.1 (#6607)
  • Prepare release notes for v1.6.1
• Github Security Advisory GHSA-crp2-qrr5-8pq7
  • Use fs.RootPath when mounting volumes
• [release/1.6] runc.v1/v2: return init pid when clean dead shim (#6572)
  • containerd-shim-runc-v1: return init pid when clean dead shim
  • containerd-shim-runc-v2: return init pid when clean dead shim

Dependency Changes

This release has no dependency changes

Previous release can be found at v1.6.0

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 main. 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 main. 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

• 10f428d Merge pull request #6607 from dmcgowan/prepare-v1.6.1
• 787b467 Prepare release notes for v1.6.1
• 075cfdf Merge pull request from GHSA-crp2-qrr5-8pq7
• 7078e50 Merge pull request #6572 from fuweid/cp-1.6-6452-6571
• 444eba4 containerd-shim-runc-v1: return init pid when clean dead shim
• 37bb915 containerd-shim-runc-v2: return init pid when clean dead shim
• 9f316fa Use fs.RootPath when mounting volumes
• 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 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 use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/openllb/hlb/network/alerts).