From Fedora Project Wiki
(Provide DNF and Bootc in Image Mode fedora variants.)
 
Line 13: Line 13:
== Summary ==
== 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?". -->
<!-- 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, 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.


== Owner ==
== Owner ==

Revision as of 16:54, 7 May 2024

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.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
Guidance
For details on how to fill out this form, see the documentation.
Report issues
To report an issue with this template, file an issue in the pgm_docs repo.


= 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, 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.

Owner

  • Name: Joseph Marrero
  • 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>


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

Feedback

Benefit to Fedora

Scope

  • Proposal owners:
  • Other developers:
  • 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

Early Testing (Optional)

Do you require 'QA Blueprint' support? Y/N

How To Test

User Experience

Dependencies

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No


Documentation

N/A (not a System Wide Change)

Release Notes