2.3. Enabling and disabling DNF plugins
In the DNF tool, plugins are loaded by default. However, you can influence which plugins DNF loads.
Every installed plugin can have its own configuration file in the /etc/dnf/plugins/ directory. Name plugin configuration files in the <plugin_name>.conf directory. By default, plugins are typically enabled. You can manage plugins by either using different dnf commands or modifying the [main] section of the plugin’s configuration file.
Disable all plugins only for diagnosing a potential problem. DNF requires certain plugins, such as product-id and subscription-manager, and disabling them causes Red Hat Enterprise Linux to not be able to install or update software from the Content Delivery Network (CDN).
Procedure
Use one of the following methods to influence how DNF uses plugins:
To enable or disable loading of DNF plugins globally, add the
pluginsparameter to the[main]section of the/etc/dnf/dnf.conffile.-
Set
plugins=1(default) to enable loading of all DNF plugins. -
Set
plugins=0to disable loading of all DNF plugins.
-
Set
To disable a particular plugin, add
enabled=Falseto the[main]section in the/etc/dnf/plugins/<plug-in_name>.conffile:[main] enabled=FalseTo disable all DNF plugins for a particular command, append the
--nopluginsoption to the command. For example, to disable DNF plugins for a single update command, enter:# dnf --noplugins updateTo disable certain DNF plugins for a single command, append the
--disableplugin=<plugin-name>option to the command. For example, to disable a certain DNF plugin for a single update command, enter:# dnf update --disableplugin=<plugin_name>To enable certain DNF plugins for a single command, append the
--enableplugin=<plugin-name>option to the command. For example, to enable a certain DNF plugin for a single update command, enter:# dnf update --enableplugin=<plugin_name>