Latest revision as of 15:27, 2 October 2024

DNF and bootc in Image Mode Fedora variants

Summary

Enhance the image-mode Fedora user experience by providing familiar DNF commands on client side and inside a container image 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, we will 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.

This work is part of the Fedora Bootable Containers Initiative.

Owner

Joseph Marrero, jmarrero@fedoraproject.org
Colin Walters
David Cantrell
Timothée Ravier, siosm@fedoraproject.org
Jonathan Lebon
Renata Ravanelli

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-10-02
Announced
Discussion thread
FESCo issue: #3216
Tracker bug: #2293627
Release notes tracker: #99

Detailed Description

Having the Fedora ecosystem (from users to release engineering) move away from DNF on image-based systems has had mixed results 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

None so far.

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: Probably nothing needed so N/A #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: Aligns with the work to improve Image Mode variants of Fedora

Upgrade/compatibility impact

Each edition/spin will 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

Inside 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

N/A

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

Release Notes

Starting Fedora 41, the Fedora Atomic Desktops, Fedora CoreOS and Fedora IOT will ship bootc and DNF5 as part of the image. Now you can use dnf commands as part of container builds that use these Fedora variants as the base image. While rpm-ostree is still available you can now use bootc to manage your image mode deployments and updates.

When running dnf on a booted image mode system dnf will give a better error message pointing to the available tools on your booted system to accomplish your task.This is the start of a process to enable dnf with rpm-ostree features and the re-focus on bootc to manage image mode deployments.

@@ Line 1: / Line 1: @@
-= DNF and bootc in Image Mode Fedora variants
+= DNF and bootc in Image Mode Fedora variants =
-{{Change_Proposal_Banner}}
 == 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.
+Enhance the image-mode Fedora user experience by providing familiar DNF commands on client side and inside a container image build. Provide DNF5 alongside rpm-ostree while we slowly port functionality from rpm-ostree to DNF5.
-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.
+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, we will 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.
+This work is part of the [https://fedoraproject.org/wiki/Initiatives/Fedora_bootc Fedora Bootable Containers Initiative].
 == Owner ==
@@ Line 20: / Line 22: @@
 This should link to your home wiki page so we know who you are.
 -->
-* Name: [[User:jmarrero| Joseph Marrero]]
+* [[User:jmarrero| Joseph Marrero]], jmarrero@fedoraproject.org
-* Name: [[User:walters| Colin Walters]]
+* [[User:walters| Colin Walters]]
-<!-- 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. -->
+* [[User:dcantrell | David Cantrell]]
-* Email: jmarrero@fedoraproject.org
+* [[User:Siosm| Timothée Ravier]], siosm@fedoraproject.org
-<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
+* [[User:jlebon| Jonathan Lebon]]
-* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
+* [[User:ravanelli| Renata Ravanelli]]
--->
 == Current status ==
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF41]]
-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
+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.
@@ Line 38: / Line 39: @@
 <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
-<!-- Select proper category, default is Self Contained Change -->
+[[Category:SystemWideChange]]
-[[Category:SelfContainedChange]]
-<!-- [[Category:SystemWideChange]] -->
 * Targeted release: [https://docs.fedoraproject.org/en-US/releases/f41/ Fedora Linux 41]
@@ Line 50: / Line 49: @@
 ON_QA -> change is fully code complete
 -->
-* [Announced]
+* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/ITBTRAJE2XORB4GZYY2JW4JNPKVX5A3F/ Announced]
-* [<will be assigned by the Wrangler> Discussion thread]
+* [https://discussion.fedoraproject.org/t/f41-change-proposal-dnf-and-bootc-in-image-mode-fedora-variants-system-wide/117664 Discussion thread]
-* FESCo issue: <will be assigned by the Wrangler>
+* FESCo issue: [https://pagure.io/fesco/issue/3216 #3216]
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2293627 #2293627]
-* Release notes tracker: <will be assigned by the Wrangler>
+* Release notes tracker: [https://gitlab.com/fedora/docs/fedora-linux-documentation/release-notes/-/issues/99 #99]
 == 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.
+Having the Fedora ecosystem (from users to release engineering) move away from DNF on image-based systems has had mixed results 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:
@@ Line 70: / Line 69: @@
 == Feedback ==
 <!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
+None so far.
 == Benefit to Fedora ==
-<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
-      Be sure to include the following areas if relevant:
-      If this is a major capability update, what has changed?
-           For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
-      If this is a new functionality, what capabilities does it bring?
-           For example: This change allows package upgrades to be performed automatically and rolled-back at will.
-      Does this improve some specific package or set of packages?
-           For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
-      Does this improve specific Spins or Editions?
-           For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
-      Does this make the distribution more efficient?
-           For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
-      Is this an improvement to maintainer processes?
-           For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
-      Is this an improvement targeted as specific contributors?
-           For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
-     When a Change has multiple benefits, it's better to list them all.
-     Consider these Change pages from previous editions as inspiration:
-     https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
-     https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
-     https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
-     https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
-     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.
@@ Line 104: / Line 79: @@
 == 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.
-  * Add DNF5 and bootc on all image-based/ostree variants.
+** Update DNF5 error message when called on a booted image-based/ostree system
-  * 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.
-* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: Probably nothing needed so N/A [https://pagure.io/releng/issues #Releng issue number]
-<!-- 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?-->
+* Policies and guidelines: N/A (not needed for this Change)
-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 -->
-<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
-The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
-* Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->
 * Trademark approval: N/A (not needed for this Change)
-<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
+* Alignment with the Fedora Strategy: Aligns with the work to improve Image Mode variants of Fedora
-* Alignment with the Fedora Strategy:
-<!-- Does your proposal align with the current Fedora Strategy: https://discussion.fedoraproject.org/t/fedora-strategy-2028-february-march-planning-work-and-roadmap-til-flock/43618 ? It's okay if it doesn't, but it's something to consider -->
 == Upgrade/compatibility impact ==
-<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+Each edition/spin will 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.
-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? No <!-- Optional Step for System-Wide Changes only -->
+Do you require 'QA Blueprint' support? No
 == How To Test ==
 <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  This can be based off of the above section if early testing has been completed. If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
@@ Line 152: / Line 114: @@
 -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+On a booted image-based host, run: `dnf install <package>` and `bootc status`
-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.
+Inside a Dockerfile/Containerfile with a image-based Fedora variant as a base image, add a package using dnf: `RUN dnf install <package>`
-RUN dnf install <package>
 == User Experience ==
-<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
- This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
- Describe what Users will see or notice, for example:
-  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
-  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- - Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- - 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 ==
-<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+N/A
-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: 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: Beta freeze.
-* Contingency deadline: beta freeze.
-<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
 * 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/
+* https://dnf5.readthedocs.io/en/latest/
+* https://containers.github.io/bootc/
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+== Release Notes ==
-N/A (not a System Wide Change)
-== Release Notes ==
 <!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are at https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/ -->
 <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
@@ Line 204: / Line 144: @@
 Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
 -->
+Starting Fedora 41, the Fedora Atomic Desktops, Fedora CoreOS and Fedora IOT will ship bootc and DNF5 as part of the image. Now you can use dnf commands as part of container builds that use these Fedora variants as the base image. While rpm-ostree is still available you can now use bootc to manage your image mode deployments and updates.
+When running dnf on a booted image mode system dnf will give a better error message pointing to the available tools on your booted system to accomplish your task.This is the start of a process to enable dnf with rpm-ostree features and the re-focus on bootc to manage image mode deployments.

Search

Changes/DNFAndBootcInImageModeFedora: Difference between revisions