1netplan-apply(8) netplan-apply(8)
2
3
4
6 netplan-apply - apply configuration from netplan YAML files to a run‐
7 ning system
8
10 netplan [--debug] apply -h | --help
11
12 netplan [--debug] apply
13
15 netplan apply applies the current netplan configuration to a running
16 system.
17
18 The process works as follows:
19
20 1. The backend configuration is generated from netplan YAML files.
21
22 2. The appropriate backends (systemd-networkd(8) or NetworkManager(8))
23 are invoked to bring up configured interfaces.
24
25 3. netplan apply iterates through interfaces that are still down, un‐
26 binding them from their drivers, and rebinding them. This gives
27 udev(7) renaming rules the opportunity to run.
28
29 4. If any devices have been rebound, the appropriate backends are re-
30 invoked in case more matches can be done.
31
32 For information about the generation step, see netplan-generate(8).
33 For details of the configuration file format, see netplan(5).
34
36 -h, --help
37 Print basic help.
38
39 --debug
40 Print debugging output during the process.
41
43 netplan apply will not remove virtual devices such as bridges and bonds
44 that have been created, even if they are no longer described in the
45 netplan configuration. That is due to the fact that netplan operates
46 statelessly and is not aware of the previously defined virtual devices.
47
48 This can be resolved by manually removing the virtual device (for exam‐
49 ple ip link delete dev bond0) and then running netplan apply, by re‐
50 booting, or by creating a temporary backup of the YAML state in
51 /etc/netplan before modifying the configuration and passing this state
52 to netplan (e.g. mkdir -p /tmp/netplan_state_backup/etc && cp -r
53 /etc/netplan /tmp/netplan_state_backup/etc/ then running netplan apply
54 --state /tmp/netplan_state_backup)
55
57 netplan(5), netplan-generate(8), netplan-try(8), udev(7), systemd-net‐
58 workd.service(8), NetworkManager(8)
59
61 Daniel Axtens (<daniel.axtens@canonical.com>).
62
63
64
65 netplan-apply(8)