.\" Automatically generated by Pandoc 2.2.1
.\"
.TH "netplan\-apply" "8" "" "" ""
.hy
.SH NAME
.PP
netplan\-apply \- apply configuration from netplan YAML files to a
running system
.SH SYNOPSIS
.PP
\f[B]netplan\f[] [\[en]debug] \f[B]apply\f[] \-h | \[en]help
.PP
\f[B]netplan\f[] [\[en]debug] \f[B]apply\f[]
.SH DESCRIPTION
.PP
\f[B]netplan apply\f[] applies the current netplan configuration to a
running system.
.PP
The process works as follows:
.IP "1." 3
The backend configuration is generated from netplan YAML files.
.IP "2." 3
The appropriate backends (\f[B]systemd\-networkd\f[](8) or
\f[B]NetworkManager\f[](8)) are invoked to bring up configured
interfaces.
.IP "3." 3
\f[B]netplan apply\f[] iterates through interfaces that are still down,
unbinding them from their drivers, and rebinding them.
This gives \f[B]udev\f[](7) renaming rules the opportunity to run.
.IP "4." 3
If any devices have been rebound, the appropriate backends are
re\-invoked in case more matches can be done.
.PP
For information about the generation step, see
\f[B]netplan\-generate\f[](8).
For details of the configuration file format, see \f[B]netplan\f[](5).
.SH OPTIONS
.TP
.B \-h, \[en]help
Print basic help.
.RS
.RE
.TP
.B \[en]debug
Print debugging output during the process.
.RS
.RE
.SH KNOWN ISSUES
.PP
\f[B]netplan apply\f[] will not remove virtual devices such as bridges
and bonds that have been created, even if they are no longer described
in the netplan configuration.
.PP
This can be resolved by manually removing the virtual device (for
example \f[C]ip\ link\ delete\ dev\ bond0\f[]) and then running
\f[B]netplan apply\f[], or by rebooting.
.SH SEE ALSO
.PP
\f[B]netplan\f[](5), \f[B]netplan\-generate\f[](8),
\f[B]netplan\-try\f[](8), \f[B]udev\f[](7),
\f[B]systemd\-networkd.service\f[](8), \f[B]NetworkManager\f[](8)
.SH AUTHORS
Daniel Axtens (<daniel.axtens@canonical.com>).