Next: Invoking guix-daemon, Previous: Binary Installation, Up: Installation [Contents][Index]
During installation, the build daemon that must be running
to use Guix has already been set up and you can run guix
commands in your terminal program, see Getting Started:
guix build hello
If this runs through without error, feel free to skip this section. You should continue with the following section, Application Setup.
However, now would be a good time to replace outdated daemon versions,
tweak it, perform builds on other machines (see Using the Offload Facility), or start it manually in special environments like “chroots”
(see Chrooting into an existing system) or WSL (not needed for WSL
images created with Guix, see wsl2-image-type). If you want to know more or optimize your
system, this section is worth reading.
Operations such as building a package or running the garbage collector
are all performed by a specialized process, the build daemon, on
behalf of clients. Only the daemon may access the store and its
associated database. Thus, any operation that manipulates the store
goes through the daemon. For instance, command-line tools such as
guix package and guix build communicate with the
daemon (via remote procedure calls) to instruct it what to do.
The following sections explain how to prepare the build daemon’s environment. See Substitutes for how to allow the daemon to download pre-built binaries.