Update moby-engine and docker-cli rpms in Fedora F42 and F41 to version 28.x.x. This will sync both releases with F43/rawhide. Prior versions are now unmaintained by the upstream project (exception noted below).
Moby Project maintainers recently marked Moby Engine and Docker CLI version 27.x as "unmaintained". Fedora 42 currently has moby-engine/docker-cli v27.5.1. Fedora 41 has moby-engine/docker-cli v27.3.1.
The moby-engine rpm provides the open source Docker runtime. The docker-cli rpm provides the Docker command line interface to the runtime.
moby-engine
docker-cli
Legacy version v25 and v23 are also maintained by Mirantis.
Moby Project version support: https://github.com/moby/moby/blob/master/project/BRANCHES-AND-TAGS.md. "The project generally attempts to adhere to Semantic Versioning whenever possible."
Seems fine with me. +1
(Do we want to consider a permanent exception?)
Metadata Update from @ngompa: - Issue tagged with: updates policy exception
TL;DR - yes for Docker CLI and Moby Engine. Also potentially for Containerd.
I have been thinking about an exception request - in the context of specifically for the moby-engine/docker-cli package (both rpms are produced by the moby-engine spec file), and also in the broader Docker ecosystem context.
The Docker context for Fedora, also includes containerd and runc and docker-compose-switch. Switch is largely "as-is" and provides the legacy docker-compose command line via an alias to the 'real' docker compose command where compose is a plug-in to the Docker CLI.
docker-compose
docker compose
compose
Another relevant factor is the Podman ecosystem which is maintained in Fedora at the current Podman, Buildah, etc version across all Fedora releases.
Given the role of containers in the larger Fedora ecosystem (docker, podman, kubernetes for developing and running container workloads and the emerging bootc model where Fedora itself is managed as a container from the end user perspective), I believe it important to product Fedora uses current container related tools in both active releases as well as in rawhide.
bootc
So I recommend an exception for moby-engine/docker-cli and an evaluation of a possible exception for Containerd (see below). Runc already functions as if it has an exception.
Containerd maintainers support two active releases (currently v2.0 and v2.1) and a Long Term Stable (LTS) release (currently v1.6 transitioning to v1.7). An active release has support for approximately 1 year. Fedora currently has v2.1.x in F43, v2.0.x in F42, v1.7.x in F41, and v1.6.x in F40. This status is consistent with the Stable Release posture for Fedora. Yet I wonder if the user community (Docker and Kubernetes would value have both active releases available as well as an LTS release somewhat similar to Kubernetes (all 3 concurrently supported versions are available). This might be especially valuable for the EPEL user base but perhaps not Fedora per se.
Runc is interesting in that all Fedora releases are currently maintained at the current runc release. I.E. it is functioning as if an exemption is in place (but perhaps not documented?). Runc maintainers do support the latest-1 release with security fixes.
runc
latest-1
Containerd: https://github.com/containerd/containerd/blob/main/RELEASES.md#support-horizon Runc: https://github.com/opencontainers/runc/blob/main/RELEASES.md
+1
+1 to permitting the current upgrade. I'm going to recommend that we separate the question of a permanent exception into another ticket to avoid confusing the votes. So if that's desired, please file another one.
Will do! thank you
Metadata Update from @fale: - Issue tagged with: meeting
APPROVED (+6, 0, -0)
Metadata Update from @fale: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Metadata Update from @fale: - Issue untagged with: meeting
Log in to comment on this ticket.