(→Scope) |
(adding tracker bug) |
||
(24 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
= DNF and bootc in Image Mode Fedora variants = | |||
== 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?". --> | ||
DNF5 can be used in most cases during container builds (Containerfile/Dockerfiles) for a familiar UX | 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, 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. | 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. | 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. | 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 == | == Owner == | ||
Line 28: | Line 22: | ||
This should link to your home wiki page so we know who you are. | This should link to your home wiki page so we know who you are. | ||
--> | --> | ||
* | * [[User:jmarrero| Joseph Marrero]], jmarrero@fedoraproject.org | ||
* [[User:walters| Colin Walters]] | |||
* | * [[User:dcantrell | David Cantrell]] | ||
* [[User:Siosm| Timothée Ravier]], siosm@fedoraproject.org | |||
* | * [[User:jlebon| Jonathan Lebon]] | ||
* [[User:ravanelli| Renata Ravanelli]] | |||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeAcceptedF41]] | ||
DNF5 when installed on a image-based/ostree system can be used to install | 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. | Bootc allows system admins to deploy bootable containers and it's available on the Fedora repositories. | ||
Line 45: | 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--> | <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--> | ||
[[Category:SystemWideChange]] | |||
* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f41/ Fedora Linux 41] | * Targeted release: [https://docs.fedoraproject.org/en-US/releases/f41/ Fedora Linux 41] | ||
Line 57: | Line 49: | ||
ON_QA -> change is fully code complete | ON_QA -> change is fully code complete | ||
--> | --> | ||
* [Announced] | * [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/ITBTRAJE2XORB4GZYY2JW4JNPKVX5A3F/ Announced] | ||
* [ | * [https://discussion.fedoraproject.org/t/f41-change-proposal-dnf-and-bootc-in-image-mode-fedora-variants-system-wide/117664 Discussion thread] | ||
* FESCo issue: | * FESCo issue: [https://pagure.io/fesco/issue/3216 #3216] | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2293627 #2293627] | ||
* Release notes tracker: <will be assigned by the Wrangler> | * Release notes tracker: <will be assigned by the Wrangler> | ||
== Detailed Description == | == 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. --> | <!-- 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 | 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: | This proposes that: | ||
Line 77: | Line 69: | ||
== Feedback == | == 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. --> | <!-- 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 == | == Benefit to Fedora == | ||
* A familiar UX for rpms during container builds of image-based 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. | * A new dedicated tool for image-based system updates management that follows the *nix ethos of using one thing and doing it well. | ||
Line 111: | Line 79: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * 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. | |||
* Other developers: | * Release engineering: Probably nothing needed so N/A [https://pagure.io/releng/issues #Releng issue number] | ||
* 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] | |||
* Policies and guidelines: N/A (not needed for this Change) | |||
* Trademark approval: 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 | |||
* Alignment with the Fedora Strategy: | |||
== Upgrade/compatibility impact == | == 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) == | == Early Testing (Optional) == | ||
Do you require 'QA Blueprint' support? | Do you require 'QA Blueprint' support? No | ||
== How To Test == | == 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. | <!-- 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 158: | Line 114: | ||
--> | --> | ||
< | 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 == | == User Experience == | ||
Users of image-based Fedora variants will be able to use the `dnf` command on Container builds and unlocked systems. | |||
== Dependencies == | == Dependencies == | ||
N/A | |||
== Contingency Plan == | == Contingency Plan == | ||
* Contingency mechanism: Continue to ship without DNF in some or all image-based/ostree variants. | |||
* Contingency mechanism: | * Contingency deadline: Beta freeze. | ||
* Blocks release? No | |||
* Contingency deadline: | |||
* Blocks release? | |||
== Documentation == | == Documentation == | ||
* https://dnf5.readthedocs.io/en/latest/ | |||
* https://containers.github.io/bootc/ | |||
== Release Notes == | == 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 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. | <!-- 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 200: | Line 144: | ||
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | 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. |
Latest revision as of 11:51, 21 June 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-06-21
- Announced
- Discussion thread
- FESCo issue: #3216
- Tracker bug: #2293627
- 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 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.