Changes/DNFAndBootcInImageModeFedora: Difference between revisions

Revision as of 17:22, 7 May 2024

= DNF and bootc in Image Mode Fedora variants

This is a proposed Change for Fedora Linux.
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

Enhance the image-mode Fedora user experience by providing familiar dnf commands on client side and inside a docker build. Provide DNF5 alongside rpm-ostree while we slowly port functionality from rpm-ostree to DNF5.

DNF5 can be used in most cases during container builds (Containerfile/Dockerfiles) for a familiar UX, initially DNF will point users to use rpm-ostree on a booted image-based/ostree system.

For Fedora 41, provide DNF5 on image-based Fedora variants (Atomic desktops, Fedora IoT, etc). We will update all layering examples to use dnf during build time when possible. Additionally to DNF we will still provide rpm-ostree as the main tool for package layering on the client side and bootc to manage transactional, in-place operating system updates using OCI/Docker container images.

DNF5 will provide a helpful error when running on an ostree/image-based booted system pointing to use rpm-ostree or to unlock the system.

Owner

Name: Joseph Marrero
Email: jmarrero@fedoraproject.org

Current status

DNF5 when installed on a image-based/ostree system can be used to install rpms if the system is unlocked, it also works on most container builds, one major exception at the moment are kernel installations and kernel updates. DNF is not part of image variants at the moment, however CoreOS is exploring adding it via: https://github.com/coreos/fedora-coreos-tracker/issues/1687

Bootc allows system admins to deploy bootable containers and it's available on the Fedora repositories.

Targeted release: Fedora Linux 41
Last updated: 2024-05-07
[Announced]
[<will be assigned by the Wrangler> Discussion thread]
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

Having the Fedora ecosystem (from users to release engineering) move away from DNF on image-based systems is not productive as it has forced sysadmins and users to not use DNF as they are accustomed to and learn a new tool to do rpm package management in their systems. This change proposal starts the process of making DNF the client side tool to manage rpms on image-based systems in the future. To start we will provide the DNF5 package alongside rpm-ostree, giving sysadmins and users the ability to use DNF on their container builds and unlocked systems running image-based Fedora variants. We will also provide bootc to manage the image-based deployments and updates.

This proposes that:

DNF5 is included on image-based/ostree Fedora variants.
DNF5 is updated to point users to rpm-ostree on booted client systems when invoked.
rpm-ostree features will start being ported to DNF5.
We support deriving new user custom images from image-based Fedora images and installing software using DNF during builds.
We ship bootc on all Fedora image-based variants.

Feedback

Benefit to Fedora

A familiar UX for rpms during container builds of image-based Fedora.
A new dedicated tool for image-based system updates management that follows the *nix ethos of using one thing and doing it well.
An initial use of DNF on booted image-based systems when the system is unlocked.

Scope

Proposal owners:

 * Add DNF5 and bootc on all image-based/ostree variants.
 * Update DNF5 error message when called on a booted image-based/ostree system

Other developers:

The "other" here is vague, but certainly developing this so far has needed cooperation with e.g. the containers, coreos and dnf organizations etc.

Release engineering: #Releng issue number

Policies and guidelines: N/A (not needed for this Change)

Trademark approval: N/A (not needed for this Change)

Alignment with the Fedora Strategy:

Upgrade/compatibility impact

Each individual edition/spin would need to include bootc and dnf(DNF5). However rpm-ostree will still be present, which means there is no upgrade/compatibility impact, we are adding additional tools not removing tools or functionality.

Early Testing (Optional)

Do you require 'QA Blueprint' support? No

How To Test

On a booted image-based host, run: dnf install <package> and bootc status

also on a Dockerfile/Containerfile with a image-based Fedora variant as a base image add a package using dnf. RUN dnf install <package>

User Experience

Users of image-based Fedora variants will be able to use the dnf command on Container builds and unlocked systems.

Dependencies

Release engineering.

Contingency Plan

Contingency mechanism: Continue to ship without DNF in some or all image-based/ostree variants.
Contingency deadline: beta freeze.
Blocks release? No

Documentation

 https://dnf5.readthedocs.io/en/latest/

 https://containers.github.io/bootc/

N/A (not a System Wide Change)

Release Notes

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | 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.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
-{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
-{{admon/tip | Report issues | To report an issue with this template, file an issue in the [https://pagure.io/fedora-pgm/pgm_docs pgm_docs repo].}}
-<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 = DNF and bootc in Image Mode Fedora variants
@@ Line 13: / Line 5: @@
 == Summary ==
 <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
+Enhance the image-mode Fedora user experience by providing familiar dnf commands on client side and inside a docker build.
+Provide DNF5 alongside rpm-ostree while we slowly port functionality from rpm-ostree to DNF5.
+DNF5 can be used in most cases during container builds (Containerfile/Dockerfiles) for a familiar UX, initially DNF will point users to use rpm-ostree on a booted image-based/ostree system.
+For Fedora 41, provide DNF5 on image-based Fedora variants (Atomic desktops, Fedora IoT, etc). We will update all layering examples to use dnf during build time when possible.
+Additionally to DNF we will still provide '''rpm-ostree''' as the main tool for package layering on the client side and '''bootc''' to manage transactional, in-place operating system updates using OCI/Docker container images.
+DNF5 will provide a helpful error when running on an ostree/image-based booted system pointing to use rpm-ostree or to unlock the system.
 == Owner ==
@@ Line 21: / Line 22: @@
 * Name: [[User:jmarrero| Joseph Marrero]]
 <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
-* Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
+* Email: jmarrero@fedoraproject.org
 <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
 -->
 == Current status ==
@@ Line 57: / Line 57: @@
 == Detailed Description ==
 <!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+Having the Fedora ecosystem (from users to release engineering) move away from DNF on image-based systems is not productive as it has forced sysadmins and users to not use DNF as they are accustomed to and learn a new tool to do rpm package management in their systems. This change proposal starts the process of making DNF the client side tool to manage rpms on image-based systems in the future. To start we will provide the DNF5 package alongside rpm-ostree, giving sysadmins and users the ability to use DNF on their container builds and unlocked systems running image-based Fedora variants. We will also provide bootc to manage the image-based deployments and updates.
+This proposes that:
+* DNF5 is included on image-based/ostree Fedora variants.
+* DNF5 is updated to point users to rpm-ostree on booted client systems when invoked.
+* rpm-ostree features will start being ported to DNF5.
+* We support '''deriving''' new user custom images from image-based Fedora images and installing software using DNF during builds.
+* We ship bootc on all Fedora image-based variants.
 == Feedback ==
@@ Line 89: / Line 98: @@
       https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
 -->
+* A familiar UX for rpms during container builds of image-based Fedora.
+* A new dedicated tool for image-based system updates management that follows the *nix ethos of using one thing and doing it well.
+* An initial use of DNF on booted image-based systems when the system is unlocked.
 == Scope ==
 * Proposal owners:
 <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+  * Add DNF5 and bootc on all image-based/ostree variants.
+  * Update DNF5 error message when called on a booted image-based/ostree system
 * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+The "other" here is vague, but certainly developing this so far has needed cooperation with e.g. the containers, coreos and dnf organizations etc.
 * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 114: / Line 129: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+Each individual edition/spin would need to include bootc and dnf(DNF5). However rpm-ostree will still be present, which means there is no upgrade/compatibility impact, we are adding additional tools not removing tools or functionality.
 == Early Testing (Optional) ==
 <!-- This is an optional step for system-wide changes to avail of. If you would like to build an initial proof of concept of your change and have a member of Fedora QA help you write and/or run some initial basic tests on your code, please email tests@fedoraproject.org and include the link to your change proposal. This step is *optional*. -->
-Do you require 'QA Blueprint' support? Y/N <!-- Optional Step for System-Wide Changes only -->
+Do you require 'QA Blueprint' support? No <!-- Optional Step for System-Wide Changes only -->
 == How To Test ==
@@ Line 136: / Line 152: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+On a booted image-based host, run:
+dnf install <package>
+and
+bootc status
+also on a Dockerfile/Containerfile with a image-based Fedora variant as a base image add a package using dnf.
+RUN dnf install <package>
 == User Experience ==
@@ Line 148: / Line 171: @@
   - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
 -->
+Users of image-based Fedora variants will be able to use the `dnf` command on Container builds and unlocked systems.
 == Dependencies ==
@@ Line 153: / Line 177: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+Release engineering.
 == Contingency Plan ==
 <!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
-* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency mechanism: Continue to ship without DNF in some or all image-based/ostree variants.
 <!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
-* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency deadline: beta freeze.
 <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Blocks release? No
 == Documentation ==
 <!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+  https://dnf5.readthedocs.io/en/latest/
+  https://containers.github.io/bootc/
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 N/A (not a System Wide Change)
 == Release Notes ==

Search