![]() variantĬorresponds to the XKBVARIANT setting. See its manual page for more details.Ĭorresponds to the XKBLAYOUT setting. The mapping’s keys correspond to settings in the /etc/default/keyboard configuration file. Often systems being automatically installed will not have a keyboard at all in which case the value used here does not matter. Type: mapping, see below default: US English keyboard can be interactive: yes Type: string default: "stable/ubuntu-$REL" Type: mapping default: see below can be interactive: yesĬontrols whether the installer updates to a new version available in the given channel before continuing. The locale to configure for the installed system. Type: string default: en_US.UTF-8 can be interactive: yes, always interactive if any section is The autoinstall config is available at /autoinstall.yaml (irrespective of how it was provided) and the file will be re-read after the early-commands have run to allow them to alter the config if necessary. ![]() Type: command list default: no commands can be interactive: noĪ list of shell commands to invoke as soon as the installer starts, in particular before probing for block and network devices. If there are any interactive sections at all, the reporting key is ignored. This documentation indicates if a given section can be interactive or not. Not all config keys correspond to screens in the UI. You can use the special section name of “*” to indicate that the installer should ask all the usual questions – in this case, the autoinstall.yaml file is not really an “autoinstall” file at all, instead just a way to change the defaults in the UI. If a value is provided for an interactive section it is used as the default. Would stop on the network screen and allow the user to change the defaults. ![]() Currently this must be “1”.Ī list of config keys to still show in the UI. ![]() Top-level keysĪ future-proofing config file version field. Any command exiting with a non-zero return code is considered an error and aborts the install (except for error-commands, where it is ignored). Each command can be a string (in which case it is executed via “sh -c”) or a list, in which case it is executed directly. Several config keys are lists of commands to be executed. SchemaĪutoinstall configs are validated against a JSON schema before they are used. At top level it must be a mapping containing the keys described in this document. Multi-node configuration with Docker-Composeĭistributed Replicated Block Device (DRBD)Īutomated Server installer config file reference Overall format ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |