.\" Man page generated from reStructuredText.
.
.
.nr rst2man-indent-level 0
.
.de1 rstReportMargin
\\$1 \\n[an-margin]
level \\n[rst2man-indent-level]
level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
-
\\n[rst2man-indent0]
\\n[rst2man-indent1]
\\n[rst2man-indent2]
..
.de1 INDENT
.\" .rstReportMargin pre:
. RS \\$1
. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
. nr rst2man-indent-level +1
.\" .rstReportMargin post:
..
.de UNINDENT
. RE
.\" indent \\n[an-margin]
.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
.nr rst2man-indent-level -1
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
..
.TH "DNF5-INSTALLROOT" "7" "Apr 18, 2025" "" "dnf5"
.SH NAME
dnf5-installroot \- Installroot Parameter
.SH DESCRIPTION
.sp
The \fB\-\-installroot\fP parameter is used to specify an alternative installroot,
relative to where all packages will be installed. Think of it like doing
\fBchroot <root> dnf\fP, except using \fB\-\-installroot\fP allows \fBDNF5\fP to work
before the chroot is created.
.sp
\fIcachedir\fP, \fIsystem_cachedir\fP, \fIlog\fP files, \fIreleasever\fP, and \fIgpgkey\fP are
taken from or stored in the installroot. OpenPGP keys are imported into the
installroot from a path relative to the host which can be specified in the
repository section of configuration files.
.sp
\fIconfiguration\fP file, \fIreposdir\fP, and \fIvars\fP are taken from inside the
installroot, unless the command\-line argument \fB\-\-use\-host\-config\fP is
passed, in which case the configuration and environment from the host system
will be used.
.sp
Note: When a path is specified within a command line argument
(\fB\-\-config=CONFIG_FILE_PATH\fP in case of \fIconfiguration\fP file,
\fB\-\-setopt=reposdir=/path/to/repodir\fP for \fIreposdir\fP,
\fB\-\-setopt=cachedir=/path/to/cachedir\fP for \fIcachedir\fP,
\fB\-\-setopt=system_cachedir=/path/to/system_cachedir\fP for \fIsystem_cachedir\fP,
\fB\-\-setopt=logdir=/path/to/logdir\fP for \fIlogdir\fP, or
\fB\-\-setopt=varsdir=/paths/to/varsdir\fP for \fIvars\fP), then this path is always
relative to the host with no exceptions. \fIpluginpath\fP and \fIpluginconfpath\fP are
relative to the host.
.sp
Note: You may also want to use the command\-line option \fB\-\-releasever=RELEASEVER\fP when creating
the installroot, otherwise the $releasever value is taken from the rpmdb within the installroot
(and thus it is empty at the time of creation and the transaction will fail). If \fB\-\-releasever=/\fP
is used, the releasever will be detected from the host (/) system. The new installroot path at the
time of creation does not contain the repository, releasever and dnf.conf files.
.sp
On a modular system you may also want to use the \fB\-\-setopt=module_platform_id=<module_platform_name:stream>\fP
command\-line option when creating the installroot, otherwise the \fBmodule_platform_id\fP value will be
taken from the \fB/etc/os\-release\fP file within the installroot (and thus it will be empty at the time of
creation, the modular dependency could be unsatisfied and modules content could be excluded).
.SH EXAMPLES
.INDENT 0.0
.TP
.B \fBdnf5 \-\-installroot=INSTALLROOT \-\-releasever=RELEASEVER install system\-release\fP
Permanently sets the \fBreleasever\fP of the system in the \fBINSTALLROOT\fP directory
to \fBRELEASEVER\fP\&.
.TP
.B \fBdnf5 \-\-installroot=INSTALLROOT \-\-setopt=reposdir=PATH \-\-config /path/dnf.conf upgrade\fP
Upgrades packages inside the installroot from a repository described by \fB\-\-setopt\fP
using configuration from \fB/path/dnf.conf\fP\&.
.UNINDENT
.SH AUTHOR
See AUTHORS.md in dnf5 source distribution.
.SH COPYRIGHT
Contributors to the dnf5 project.
.\" Generated by docutils manpage writer.
.