Skip to content

Conversation

@linuxmunchies
Copy link

Description

With the widespread adoption of DNF5, I propose updating the Docker installation documentation to reflect modern package management standards on Fedora. I noticed a previous attempt to do DNF5 documentation (referencing #21037) ended in failure because the addrepo command was used incorrectly, referencing an older DNF3-4 notation instead of proper DNF5 addrepo --from-repofile= notation. I have corrected this mistake and suggest this quick documentation update since Fedora 42 will be in beta soon, encouraging more users to update to 41/42, where DNF5 will be the standard format going forward. I have also included the older command for legacy systems so that both cases are covered.

I tested this change on a Fedora 41 KDE VM, and it works as expected. Since DNF5 is a complete rewrite in C++, replacing the Python-based DNF3/4, it offers improved performance and memory efficiency. Updating the documentation will help prevent confusion for users writing installation scripts while ensuring compatibility with the latest Fedora releases.

Requested Review

Please double-check to verify that I completed the auto-formatting URL correctly following Fedora's documentation standards, so it will be formatted properly on the website! Thanks!

…DNF3 instructions as backup

## Description
With the widespread adoption of DNF5, I propose updating the Docker installation documentation to reflect modern package management standards on Fedora. I noticed a previous attempt to do DNF5 documentation (referencing #21037) ended in failure because the addrepo command was used incorrectly, referencing an older DNF3-4 notation instead of proper DNF5 `addrepo --from-repofile=` notation. I have corrected this mistake and suggest this quick documentation update since Fedora 42 will be in beta soon, encouraging more users to update to 41/42, where DNF5 will be the standard format going forward. I have also included the older command for legacy systems so that both cases are covered.

I tested this change on a Fedora 41 KDE VM, and it works as expected. Since DNF5 is a complete rewrite in C++, replacing the Python-based DNF3/4, it offers improved performance and memory efficiency. Updating the documentation will help prevent confusion for users writing installation scripts while ensuring compatibility with the latest Fedora releases.

## Requested Review

Please double-check to verify that I completed the URL correctly following Fedora's documentation standards, so it will be formatted properly on the website! Thanks!
@github-actions github-actions bot added area/engine Issue affects Docker engine/daemon area/install Relates to installing a product labels Mar 10, 2025
@netlify
Copy link

netlify bot commented Mar 10, 2025

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit fda7265
🔍 Latest deploy log https://app.netlify.com/sites/docsdocker/deploys/67cf28e4a061310007324e2f
😎 Deploy Preview https://deploy-preview-22219--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Comment on lines +84 to +86
your DNF repositories) and set up the repository. Note that Fedora 41 and later
primarily use DNF5. For Fedora 40 and earlier, please use the commands below
made specifically for Fedora <=40.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should keep the "old" commands until Fedora 40 reaches EOL, that way we don't have to describe two separate ways to do this (as the installation guide already is quite complex due to many steps)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds like a suitable solution. The main reason I was driven to make this pull request was to make it easier for people building Fedora 41/42 setup scripts while referencing official docker documentation. Once F40 reaches EOL it'd be a great time to revisit this potentially, or perhaps a bit before that.

@docker-robot
Copy link

docker-robot bot commented Aug 2, 2025

Thanks for the pull request. We'd like to make our product docs better, but haven’t been able to review all the suggestions.
As our docs have also diverged, we do not have the bandwidth to review and rebase old pull requests.

If the updates are still relevant, review our contribution guidelines and rebase your pull request against the latest version of the docs, then mark it as fresh with a /remove-lifecycle stale comment.
If not, this pull request will be closed in 30 days. This helps our maintainers focus on the active pull requests.

Prevent pull requests from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

@linuxmunchies linuxmunchies closed this by deleting the head repository Sep 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/engine Issue affects Docker engine/daemon area/install Relates to installing a product lifecycle/frozen

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants