lxc-update-config detects any legacy configuration keys in the
given config file and will replace them with the appropriate new
lxc-update-config will first create a backup of the old config
file in the same directory and name it config.backup and then
update the original config file in place. In case the update
fails to apply or leads to an invalid config file that cannot be
used to start a container users can either compare config with
config.backup and try to manually repair any the invalid
configuration keys or simply rollback to the legacy configuration
file by copying config.backup to config.
Any failures for lxc-update-config to generate a useable config
file are a bug and should be reported upstream.
This page is part of the lxc (Linux containers) project.
Information about the project can be found at
⟨http://linuxcontainers.org/⟩. If you have a bug report for this
manual page, send it to email@example.com.
This page was obtained from the project's upstream Git repository
⟨https://github.com/lxc/lxc.git⟩ on 2023-12-22. (At that time,
the date of the most recent commit that was found in the
repository was 2023-12-18.) If you discover any rendering
problems in this HTML version of the page, or you believe there
is a better or more up-to-date source for the page, or you have
corrections or improvements to the information in this COLOPHON
(which is not part of the original manual page), send a mail to