The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
For details on how to fill out this form, see the documentation.
To report an issue with this template, file an issue in the pgm_docs repo.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
This change will disable i686 rpm builds for Podman, Buildah, Skopeo and related tools for active and future Fedora releases.
Owner
- Name: Lokesh Mandvekar
Current status
- Targeted release: Fedora Linux 36, Fedora Linux 37, Fedora Linux 38
- Last updated: 2023-02-07
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
Podman and related tools often don't build on i686 architecture because of underlying issues in dependencies which can be very time-consuming to fix and not worth the effort given the already miniscule usage on i686 devices, if any. Most recent build issue being with netavark v1.5.0.
Complete list of packages which will have i686 disabled:
- aardvark-dns
- buildah
- catatonit
- conmon
- crun
- fuse-overlayfs
- netavark
- oci-seccomp-bpf-hook
- podman
- skopeo
- slirp4netns
Feedback
The earlier plan was to disable both i686 and armhfp, but that would break Fedora 36 IoT armhfp, so we're only thinking of disabling i686 builds for now. Other feedback suggested filing a SelfContainedChange so here we are.
Benefit to Fedora
This change only disable i686 architecture builds, so this can help to get newer versions of podman and related tools shipped quicker.
Scope
- Proposal owners:
- Other developers:
- Release engineering: #Releng issue number
Upgrade/compatibility impact
With this change, users on i686 will not be able to get newer versions of said container tools, but upgrades to newer versions of Fedora should themselves not be affected.
How To Test
0. What special hardware / data / etc. is needed (if any)?
N/A
1. How do I prepare my system to test this change? What packages need to be installed, config files edited, etc.?
N/A
2. What specific actions do I perform to check that the change is working like it's supposed to?
You should not find any new i686 builds after this change is complete.
3. What are the expected results of those actions?
i686 users won't get any new builds.
User Experience
Any i686 user will be unable to upgrade to newer versions of Podman and related tools.
Dependencies
From dnf repoquery (skipping noarch packages and packages belonging to containers org):
- apptainer
- copr-builder
- kiwi-systemdeps-containers
- krunvm
- nbdkit-cdi-plugin
- quadlet
- rpm-ostree
- toolbox
Contingency Plan
We can try to revert if feasible.
Documentation
N/A (not a System Wide Change)