chore(deps): Bump github.com/containerd/containerd from 1.5.9 to 1.6.4

[dependabot]

Bumps github.com/containerd/containerd from 1.5.9 to 1.6.4.

Release notes

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

containerd 1.6.4

Welcome to the v1.6.4 release of containerd!

The fourth patch release for containerd 1.6 includes two fixes for CNI and SELinux.

Notable Updates

• Update go-cni to fix teardown regression (#6877)
• Fix broken SELinux relabeling for Kubernetes volume mounts (#6878)

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

• Mike Brown
• Kazuyoshi Kato
• Michael Zappa
• Wang Bing
• Wei Fu
• Antonio Ojea
• Derek McGowan
• Henry Wang
• Nabeel Rana
• Phil Estes

Changes

• Prepare release notes for 1.6.4 (#6887)
  • 0d1d2953b Prepare release notes for 1.6.4
• [release/1.6 backport] Bump opencontainers/selinux from 1.10.0 to 1.10.1 (#6878)
  • 42d691fe6 Bump opencontainers/selinux from 1.10.0 to 1.10.1
• [release/1.6] Update go-cni to v1.1.5 backported due to conflict in go.mod (#6877)
  • e9f22e008 Update go-cni to v1.1.5
• [release/1.6] cri: close fifos when container is deleted (#6859)
  • be4909e95 cri: close fifos when container is deleted

Changes from containerd/go-cni

• bump github.com/containernetworking/cni v1.1.0 (#98)
  • e24193e bump github.com/containernetworking/cni v1.1.0
• Revert "Update loopback version to support check" (#96)

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

• 212e8b6 Merge pull request #6887 from dmcgowan/prepare-1.6.4
• 0d1d295 Prepare release notes for 1.6.4
• db40e21 Merge pull request #6878 from thaJeztah/1.6_backport_bump-opencontainers_seli...
• 42d691f Bump opencontainers/selinux from 1.10.0 to 1.10.1
• 6eeeaad Merge pull request #6877 from MikeZappa87/update-go-cni-v2
• e9f22e0 Update go-cni to v1.1.5
• 50e2446 Merge pull request #6859 from fuweid/cp-16-6842
• be4909e cri: close fifos when container is deleted
• f830866 Merge pull request #6844 from dmcgowan/prepare-1.6.3
• baa386d Prepare release notes for v1.6.3
• 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)

[Callisto13]

We can't have this one right now, as it will bump github.com/containernetworking/cni to v1.1.0.
firecracker-microvm/firecracker-go-sdk version 0.22.0 still relies on 0.8.1 as it uses a package which was removed in cni 1.1.0. They are up to date on main, so we have to wait for the release of 0.23.0.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.