kraftto your preferences. In this document, we outline where configuration is stored and what the options mean, including possible values and best practices.
When you install
kraft, it will create a number of directories and files on
your host that are used for configuraiton purposes and to store cache
The default location for user configuration for
kraft is stored
~/.config/kraftkit/config.yaml. This file can be edited to your
liking or to suite your needs. Below is an overview of each configuration
option, how to set its value, their default value and purpose.
|Option||Environmental Variable||Global CLI flag||Default Value|
|Do not prompt for user interaction|
|Do not run internal tasks in parallel|
|Do not check for updates|
|System pager to pipe output to|
|Directory for placing runtime files (e.g. pidfiles)|
|Address of containerd daemon socket|
|Path to KraftKit config directory|
|Path to Unikraft manifest cache|
|Path to Unikraft component cache|
|Log level verbosity|
|Enable log timestamps|
|Log type (choice of |
|Paths to mirrors of Unikraft component artifacts|
|Paths to package or component manifests|
To increase compatibility across systems and to respect to pre-defined user
kraft recognizes the following additional environmental
|How the output is rendered in some commands. Can be set to |
|Do not use any ANSI or truecolor output in any log messaging.|
|Same as |
|Path to the general configuration directory. Affects the default value of |
|Path to the generate state directory.|
|Path to the general data directory. Affects the default value of |
The following are a few additional recommendations for global configuration values given certain contexts, environments or scenarios:
jsonto allow for better readability. KraftKit should recognize pseudo TTY environments and dynamically adjust.
basiclog type and to set the log level to
debugto get a better understanding of what's being run underneath by KraftKit.
Feel free to ask questions, report issues, and meet new people.