I think you have two options:
1) Workaround by adding /etc/netplan/xxx.yaml (or any other name which lexically sorts after "enp1s0.yaml"):
network:
version: 2
renderer: NetworkManager
ethernets:
enp1s0:
dhcp4: true
2) Cleanup dropbear-initramfs interfaces (as described at "Ask Ubuntu"):
/etc/initramfs-tools/scripts/init-bottom/deconfigure-interfaces:
rm -f /run/netplan/enp1s0.yaml && ip -f inet address flush dev enp1s0
You probably need to run 'update-initramfs -u' afterwards again...
IMO option (2) is actually a proper solution, this is why I am assigning this bug to 'dropbear', as I think it should automatically cleanup the interfaces/configs it created, once they are not needed anymore.
Hi Yannik,
I think you have two options: xxx.yaml (or any other name which lexically sorts after "enp1s0.yaml"):
1) Workaround by adding /etc/netplan/
network:
version: 2
renderer: NetworkManager
ethernets:
enp1s0:
dhcp4: true
2) Cleanup dropbear-initramfs interfaces (as described at "Ask Ubuntu"): tools/scripts/ init-bottom/ deconfigure- interfaces: enp1s0. yaml && ip -f inet address flush dev enp1s0
/etc/initramfs-
rm -f /run/netplan/
You probably need to run 'update-initramfs -u' afterwards again...
IMO option (2) is actually a proper solution, this is why I am assigning this bug to 'dropbear', as I think it should automatically cleanup the interfaces/configs it created, once they are not needed anymore.