'\" -*- coding: us-ascii -*-
.if \n(.g .ds T< \\FC
.if \n(.g .ds T> \\F[\n[.fam]]
.de URL
\\$2 \(la\\$1\(ra\\$3
..
.if \n(.g .mso www.tmac
.TH lxc-update-config 1 2019-04-14 "" ""
.SH NAME
lxc-update-config \- update a legacy pre LXC 2.1 configuration file 
.SH SYNOPSIS
'nh
.fi
.ad l
\fBlxc-update-config\fR \kx
.if (\nx>(\n(.l/2)) .nr x (\n(.l/5)
'in \n(.iu+\nxu
{-c \fIconfig\fR}
'in \n(.iu-\nxu
.ad b
'hy
.SH DESCRIPTION
\fBlxc-update-config\fR detects any legacy
configuration keys in the given \fIconfig\fR
file and will replace them with the appropriate new configuration
keys.
.PP
\fBlxc-update-config\fR will first create a backup of
the old \fIconfig\fR file in the same directory
and name it \fIconfig.backup\fR and then update
the original \fIconfig\fR file in place. In
case the update fails to apply or leads to an invalid
\fIconfig\fR file that cannot be used to start
a container users can either compare
\fIconfig\fR with
\fIconfig.backup\fR and try to manually repair
any the invalid configuration keys or simply rollback to the legacy
configuration file by copying
\fIconfig.backup\fR to
\fIconfig\fR.
.PP
Any failures for \fBlxc-update-config\fR to generate a
useable \fIconfig\fR file are a bug and should
be reported upstream.
.SH OPTIONS
.TP 
\*(T<\fB\-c, \-\-config\fR\*(T> 
Path to the configuration file to update.
.TP 
\*(T<\fB\-h, \-\-help\fR\*(T> 
.SH "SEE ALSO"
\fBlxc\fR(7),
\fBlxc-create\fR(1),
\fBlxc-copy\fR(1),
\fBlxc-destroy\fR(1),
\fBlxc-start\fR(1),
\fBlxc-stop\fR(1),
\fBlxc-execute\fR(1),
\fBlxc-console\fR(1),
\fBlxc-monitor\fR(1),
\fBlxc-wait\fR(1),
\fBlxc-cgroup\fR(1),
\fBlxc-ls\fR(1),
\fBlxc-info\fR(1),
\fBlxc-freeze\fR(1),
\fBlxc-unfreeze\fR(1),
\fBlxc-attach\fR(1),
\fBlxc.conf\fR(5)
.SH AUTHOR
Christian Brauner <\*(T<christian.brauner@ubuntu.com\*(T>>