23.0.13¶
Release date |
Name |
Upstream release |
|---|---|---|
2024-JUNE-18 |
MCR 23.0.13 |
Moby 23.0.13 and Docker CLI 23.0.10 |
Changelog¶
MCR 23.0.13 comprises the Moby 23.0.13 upstream release.
Changes specific to MCR¶
MCR contains the following component updates:
containerd
1.6.32
Changes from upstream¶
The upstream pull requests detailed in the sections that follow are those that pertain to the MCR product. For the complete list of changes and pull requests upstream, refer to the GitHub milestones.
What is new
The MCR 23.0.13 patch release focuses on the delivery of CVE and bug fixes.
Bug fixes
moby/moby#37175 Docker node promote failing.
containerd/containerd#10234 Handle unsupported config versions.
containerd/containerd#10212 Preserve CL_UNPRIVILEGED locked flags during remount of bind mounts.
containerd/containerd#10199 Update metadata snapshotter to lease on already exists.
containerd/containerd#10130 Update apparmor template to allow confined runc to kill containers
containerd/containerd#10103 Prevent GC from schedule itself with 0 period.
containerd/containerd#9993 Configure otel from env instead of config.toml.
containerd/containerd#10127 Fix snapshotter root path when not under containerd root.
containerd/containerd#10119 Fix CreatedAt time set to 269 years ago if create network failed.
containerd/containerd#10045 Fix unexpected order of mounts.
containerd/containerd#10113 Update HTTP fallback to better account for TLS timeout and previous attempts.
containerd/containerd#10064 Fix use of invalid token on retry fetching layer.
Deprecations
containerd/containerd#9993 Configure otel from env instead of config.toml.
GitHub milestones¶
The GitHub milestones offer full detail on the pull requests and changes as they correlate to the upstream Moby 23.0.13 release:
Major component versions¶
Version detail for the major components that comprise MCR 23.0.13 is presented in the table below:
Component |
Version |
|---|---|
Fipster (Go runtime) |
|
Known issues¶
Known issues that apply to Moby 23.0.13 and thus also to MCR 23.0.13 include:
moby/moby#47728 The DNS records for containers on a node that has restarted may not be resolvable by containers on other nodes on the same overlay network. This may also occur without a daemon restart, if the underlay network is experiencing packet loss at the time the container is started. Only recently uncovered, this has been an issue since the advent of the NetworkDB moby component.