Skip to content

Configuration

urunc supports configuration through a TOML configuration file that allows you to customize various runtime behaviors including logging, timestamping, and hypervisor defaults. This document explains how to configure urunc using the configuration file.

Configuration File LocationπŸ”—

urunc looks for its configuration file at /etc/urunc/config.toml. If the file doesn't exist or contains invalid configuration, urunc will use sensible defaults and continue to operate normally.

Configuration File FormatπŸ”—

The configuration file uses the TOML format and is organized into several sections:

[log]
level = "info"
syslog = false

[timestamps]
enabled = false
destination = "/var/log/urunc/timestamps.log"

[hypervisors.qemu]
default_memory_mb = 512
default_vcpus = 2
binary_path = "/usr/bin/qemu-system-x86_64"

[hypervisors.firecracker]
default_memory_mb = 256
default_vcpus = 1
binary_path = "/usr/local/bin/firecracker"

[hypervisors.hvt]
default_memory_mb = 256
default_vcpus = 1

[hypervisors.spt]
default_memory_mb = 256
default_vcpus = 1

Configuration SectionsπŸ”—

Log ConfigurationπŸ”—

The [log] section controls logging behavior for urunc:

Option Type Default Description
level string "info" Log level. Valid values: "trace", "debug", "info", "warn", "error", "fatal", "panic"
syslog boolean false Enable syslog output in addition to stderr

Example:

[log]
level = "debug"
syslog = true

Note: The effective log level is determined by both the configuration file and the command-line --debug flag.
- If --debug is not specified, the log level from the configuration file is used.
- If --debug is specified, the effective log level is the more verbose of: - the configuration file’s log level, and
- "debug" (the level implied by the flag).

For example:
- Config: "warn", CLI: --debug β†’ effective level = "debug"
- Config: "trace", CLI: --debug β†’ effective level = "trace"
- Config: "error", no --debug β†’ effective level = "error"

Timestamps ConfigurationπŸ”—

The [timestamps] section controls timestamp logging for performance monitoring:

Option Type Default Description
enabled boolean false Enable timestamp logging for performance metrics
destination string "/var/log/urunc/timestamps.log" File path where timestamps will be written

Example:

[timestamps]
enabled = true
destination = "/tmp/urunc-timestamps.log"

When enabled, urunc will log performance timestamps to help with debugging and optimization.

Hypervisor ConfigurationπŸ”—

The [hypervisors] section allows you to configure default settings for different hypervisors/VMMs. Each hypervisor is configured as a subsection with its own default values.

Supported HypervisorsπŸ”—

  • qemu - QEMU/KVM virtualization
  • firecracker - Amazon Firecracker microVM
  • hvt - Solo5 hvt (hardware virtualized tender)
  • spt - Solo5 spt (sandboxed process tender)

Hypervisor OptionsπŸ”—

Each hypervisor subsection supports the following options:

Option Type Default Description
default_memory_mb integer 256 Default memory allocation in megabytes
default_vcpus integer 1 Default number of virtual CPUs
binary_path string (empty) Optional custom path to the hypervisor binary. If not specified, urunc will search for the binary in PATH

Example:

[hypervisors.qemu]
default_memory_mb = 1024
default_vcpus = 4
binary_path = "/usr/local/bin/qemu-system-x86_64"

[hypervisors.firecracker]
default_memory_mb = 512
default_vcpus = 2
binary_path = "/opt/firecracker/firecracker"

Creating the Configuration FileπŸ”—

To create a configuration file, you can:

  1. Create the directory structure:

    sudo mkdir -p /etc/urunc
    
  2. Create the configuration file:

sudo tee /etc/urunc/config.toml > /dev/null <<EOF
[log]
level = "info"
syslog = false

[timestamps]
enabled = false
destination = "/var/log/urunc/timestamps.log"

[hypervisors.qemu]
default_memory_mb = 512
default_vcpus = 2

[hypervisors.firecracker]
default_memory_mb = 256
default_vcpus = 1

[hypervisors.hvt]
default_memory_mb = 256
default_vcpus = 1

[hypervisors.spt]
default_memory_mb = 256
default_vcpus = 1
EOF

Configuration ValidationπŸ”—

urunc will validate the configuration file when it starts. If the configuration file:

  • Does not exist: urunc uses default values and logs a warning
  • Contains syntax errors: urunc uses default values and logs a warning about the parsing error
  • Contains invalid values: urunc will either use default values for invalid fields or fail to start if critical errors are found

Default ValuesπŸ”—

If no configuration file is provided, urunc uses these default values:

[log]
level = "info"
syslog = false

[timestamps]
enabled = false
destination = "/var/log/urunc/timestamps.log"

[hypervisors.qemu]
default_memory_mb = 256
default_vcpus = 1
# binary_path is not set by default - urunc will search in PATH

[hypervisors.firecracker]
default_memory_mb = 256
default_vcpus = 1
# binary_path is not set by default - urunc will search in PATH

[hypervisors.hvt]
default_memory_mb = 256
default_vcpus = 1
# binary_path is not set by default - urunc will search in PATH

[hypervisors.spt]
default_memory_mb = 256
default_vcpus = 1
# binary_path is not set by default - urunc will search in PATH

NotesπŸ”—

  • The configuration file is only fully loaded during urunc create. The configuration options' values are then stored as Annotations in the state.json file inside the respective container's bundle. For subsequent urunc commands (such as start, kill, etc.), configuration options are loaded from the state.json annotations. In that way, all urunc configuration values except logging configuration and timestamping (see below) remain the same throughout the specific container lifecycle.
  • The configuration file is partially loaded every time urunc is invoked to parse the logging configuration and timestamping options. This way, the user has fine-grained control over the logging level and whether to redirect urunc logs to syslog. Similarly, the user can enable and disable timestamping.