chore(deps): bump github.com/containerd/containerd/v2 from 2.2.0 to 2.3.0

[dependabot]

Bumps github.com/containerd/containerd/v2 from 2.2.0 to 2.3.0.

Release notes

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

containerd 2.3.0

Welcome to the v2.3.0 release of containerd!

The third minor release of containerd 2.x focuses on continued stability alongside new features and improvements. This is the third time-based release for containerd.

Starting with containerd 2.3, the project has moved to release cadence aligned with the Kubernetes release schedule, with new minor releases about every 4 months. The containerd 2.3 release is also the first annual LTS (Long Term Stable) release under this new schedule, with support planned for at least two years. Direct upgrades between sequential LTS releases (e.g., 1.7 to 2.3) will be tested and supported.

Highlights

• Add transfer types for container filesystem copy (#13165)
• Add option to inject trace ID to logs (#13117)
• Propagate OpenTelemetry traces in outgoing RPCs from plugin clients (#13113)
• Update plugin config migration to run on load (#12608)
• Update sandbox API to include spec field (#12840)

Container Runtime Interface (CRI)

• Allow containers to use user namespaces with host networking (#12518)
• Wire UpdatePodSandboxResources to Sandbox API (#13118)
• Unpack images with per-layer labels for specific runtime (#12835)
• Populate ImageId field in container status (#12787)
• Set annotations parameter in CreateSandbox request (#12566)
• Add background stats collector to calculate UsageNanoCores for containers and pod sandboxes (#12629)

Image Distribution

• Support zstd-wrapped EROFS layers (#13185)
• Add os.features support for EROFS native container images (#13091)
• Add EROFS layer media type (#12567)

Image Storage

• Add dmverity support to the erofs snapshotter (#12502)
• Use fsmount API to avoid PAGE_SIZE limit for erofs (#12783)

Node Resource Interface (NRI)

• Pass container user (uid, gids) to plugins (#12769)
• Pass seccomp policy to plugins (#12768)
• Pass any POSIX rlimits to plugins (#12765)
• Pass extended container status to NRI. (#12770)
• Pass injected CDI devices to plugins (#12767)
• Pass linux sysctl to plugins (#12766)
• Use dedicated RPC calls for all pod and container life-cycle events via the NRI wire protocol (containerd/nri#274)
• Add basic metrics collection for the NRI framework (containerd/nri#277)

... (truncated)

Changelog

Sourced from github.com/containerd/containerd/v2'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.

Release Cadence

Since containerd v2.3 in April 2026, minor releases are provided on a time basis with a cadence of 4 months. New minor releases are scheduled for April, August, and December of each year. This cadence is synchronized with the Kubernetes release schedule to ensure that new features in containerd can be smoothly adopted by new Kubernetes releases.

The maintainers will maintain a roadmap and milestones for each release, however,

... (truncated)

Commits

• 2976f38 Merge pull request #13325 from dmcgowan/prepare-v2.3.0
• 77eeb2d Prepare release notes for v2.3.0
• c55ada3 Update api to v1.11.0
• ebf4404 Update release document
• f49640e Merge pull request #13321 from dmcgowan/remove-erofs-fsmerge-threshold
• e3d5fe8 Merge pull request #13322 from dmcgowan/prepare-api-v1.11.0
• ee17fa1 Merge pull request #13317 from fuweid/fix-merge-issue
• b7f8c35 erofs: remove fsmerge threshold from snapshotter
• 8f2fce4 Prepare release notes for v1.11.0
• ce2955c Merge pull request #13319 from mxpv/depr
• Additional commits viewable in compare view

[dependabot]

Superseded by #118.