# netplan-apply(8) - man - phpMan

[netplan-apply(8)](https://www.chedong.com/phpMan.php/man/netplan-apply/8/markdown)                                                                    [netplan-apply(8)](https://www.chedong.com/phpMan.php/man/netplan-apply/8/markdown)



## NAME
       netplan-apply - apply configuration from netplan YAML files to a running system

## SYNOPSIS
       **netplan** [--debug] **apply** -h | --help

       **netplan** [--debug] **apply**

## DESCRIPTION
       **netplan** **apply** applies the current netplan configuration to a running system.

       The process works as follows:

       1. The backend configuration is generated from netplan YAML files.

       2. The  appropriate  backends ([**systemd-networkd**(8)](https://www.chedong.com/phpMan.php/man/systemd-networkd/8/markdown) or [**NetworkManager**(8)](https://www.chedong.com/phpMan.php/man/NetworkManager/8/markdown)) are invoked to bring
          up configured interfaces.

       3. **netplan** **apply** iterates through interfaces that are still down, unbinding them  from  their
          drivers, and rebinding them.  This gives [**udev**(7)](https://www.chedong.com/phpMan.php/man/udev/7/markdown) renaming rules the opportunity to run.

       4. If  any  devices  have  been rebound, the appropriate backends are re-invoked in case more
          matches can be done.

       For information about the generation step, see [**netplan-generate**(8)](https://www.chedong.com/phpMan.php/man/netplan-generate/8/markdown).  For details of the  con‐
       figuration file format, see [**netplan**(5)](https://www.chedong.com/phpMan.php/man/netplan/5/markdown).

## OPTIONS
### -h, --help
              Print basic help.

### --debug
              Print debugging output during the process.

## KNOWN ISSUES
       **netplan** **apply** will not remove virtual devices such as bridges and bonds that have been creat‐
       ed, even if they are no longer described in the netplan configuration.  That is  due  to  the
       fact that netplan operates statelessly and is not aware of the previously defined virtual de‐
       vices.

       This can be resolved by manually removing the virtual device (for example ip link delete  dev
       bond0) and then running **netplan** **apply**, by rebooting, or by creating a temporary backup of the
       YAML state in /etc/netplan before modifying the configuration and passing this state to  net‐
       plan   (e.g.    mkdir  -p  /tmp/netplan_state_backup/etc  &&  cp  -r  /etc/netplan  /tmp/net‐
       plan_state_backup/etc/ then running **netplan** **apply** **--state** **/tmp/netplan**___**state**___**backup**)

## SEE ALSO
       [**netplan**(5)](https://www.chedong.com/phpMan.php/man/netplan/5/markdown), [**netplan-generate**(8)](https://www.chedong.com/phpMan.php/man/netplan-generate/8/markdown), [**netplan-try**(8)](https://www.chedong.com/phpMan.php/man/netplan-try/8/markdown), [**udev**(7)](https://www.chedong.com/phpMan.php/man/udev/7/markdown),  [**systemd-networkd.service**(8)](https://www.chedong.com/phpMan.php/man/systemd-networkd.service/8/markdown),  **Net**‐‐
       [**workManager**(8)](https://www.chedong.com/phpMan.php/man/workManager/8/markdown)

## AUTHORS
       Daniel Axtens (<<daniel.axtens@canonical.com>>).



                                                                                    [netplan-apply(8)](https://www.chedong.com/phpMan.php/man/netplan-apply/8/markdown)