I created a file /etc/initramfs-tools/scripts/init-bottom/deconfigure-interfaces:
#!/bin/sh
rm -f /run/netplan/*
-----
That works fine as a workaround! Flushing the device is not needed.
> 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.
The package is called 'dropbear-initramfs', not dropbear.
I checked what dropbear-initramfs is doing:
It installs a script `/usr/share/initramfs-tools/scripts/init-premount/dropbear` , which uses the function `configure_networking()` defined in `/usr/share/initramfs-tools/scripts/functions`.
The latter script is owned by the `initramfs-tools-core` package.
I would assign this bug to that package, as it should imo take care of leaving the networking it has setup in a sane state when starting the OS proper.
I created a file /etc/initramfs- tools/scripts/ init-bottom/ deconfigure- interfaces:
#!/bin/sh
rm -f /run/netplan/*
-----
That works fine as a workaround! Flushing the device is not needed.
> 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.
The package is called 'dropbear- initramfs' , not dropbear.
I checked what dropbear-initramfs is doing: initramfs- tools/scripts/ init-premount/ dropbear` , which uses the function `configure_ networking( )` defined in `/usr/share/ initramfs- tools/scripts/ functions` .
It installs a script `/usr/share/
The latter script is owned by the `initramfs- tools-core` package.
I would assign this bug to that package, as it should imo take care of leaving the networking it has setup in a sane state when starting the OS proper.