table of contents
- bullseye 2020.8-2+deb11u1
- testing 2022.7-2
- unstable 2022.7-2
- experimental 2023.3-1
ostree.repo-config - OSTree repository configuration
The config file in an OSTree repository is a "keyfile" in the XDG Desktop Entry Specification format. It has several global flags, as well as zero or more remote entries which describe how to access remote repositories.
See ostree.repo(5) for more information about OSTree repositories.
[CORE] SECTION OPTIONS¶
Repository-global options. The following entries are defined:
If you disable fsync, OSTree will no longer be robust against kernel crashes or power loss.
You might choose to disable this for local development repositories, under the assumption they can be recreated from source. Similarly, you could disable for a mirror where you could re-pull.
For the system repository, you might choose to disable fsync if you have uninterruptable power supplies and a well tested kernel.
If min-free-space-size is set to a non-zero value, min-free-space-percent is ignored. Note that, min-free-space-percent is not enforced on metadata objects. It is assumed that metadata objects are relatively small in size compared to content objects and thus kept outside the scope of this option.
If this option is set to a non-zero value, and min-free-space-percent is also set, this option takes priority. Note that, min-free-space-size is not enforced on metadata objects. It is assumed that metadata objects are relatively small in size compared to content objects and thus kept outside the scope of this option.
This only applies to repositories that use a remotes configuration directory such as system ostree repositories, which use /etc/ostree/remotes.d. Non-system repositories do not use a remotes configuration directory unless one is specified when the repository is opened.
Since 2020.7 OSTree can use delta indexes outside the summary file, making the summary file smaller (especially for larger repositories). However by default we still create the index in the summary file to make older clients work. If you know all clients will be 2020.7 later you can enable this to save network bandwidth.
[REMOTE NAME"] SECTION OPTIONS"¶
Describes a remote repository location.
[SYSROOT] SECTION OPTIONS¶
Options for the sysroot, which contains the OSTree repository, deployments, and stateroots. The following entries are defined:
If none, then OSTree will generate only BLS (Boot Loader Specification) fragments in sysroot/boot/loader/entries/ for the deployment.
If auto, then in addition to generating BLS fragments, OSTree will dynamically check for the existence of grub2, uboot, and syslinux bootloaders. If one of the bootloaders is found, then OSTree will generate a config for the bootloader found. For example, grub2-mkconfig is run for the grub2 case.
A specific bootloader type may also be explicitly requested by choosing grub2, syslinux, uboot or zipl.
In addition to the /ostree/repo/config file, remotes may also be specified in /etc/ostree/remotes.d. The remote configuration file must end in .conf; files whose name does not end in .conf will be ignored.
Originally, OSTree had just a url option for remotes. Since then, the contenturl option was introduced. Both of these support file, http, and https schemes.
Additionally, both of these can be prefixed with the string mirrorlist=, which instructs the client that the target url is a "mirrorlist" format, which is a plain text file of newline-separated URLs. Earlier URLs will be given precedence.
Note that currently, the tls-ca-path and tls-client-cert-path options apply to every HTTP request, even when contenturl and/or mirrorlist are in use. This may change in the future to only apply to metadata (i.e. url, not contenturl) fetches.
PER-REMOTE GPG KEYRINGS AND VERIFICATION¶
OSTree supports a per-remote GPG keyring, as well as a gpgkeypath option. For more information see ostree(1). in the section GPG verification.
PER-REMOTE HTTP COOKIES¶
Some content providers may want to control access to remote repositories via HTTP cookies. The ostree remote add-cookie and ostree remote delete-cookie commands will update a per-remote lookaside cookie jar, named $remotename.cookies.txt.
- XDG Desktop Entry Specification