the mentioned out of the box debian 10 image does indeed have ifupdown installed. after the initial boot i see ifupdown tools available and systemd-networkd is available too, but the service is disabled. unfortunately removing ifupdown wont realy help as it would remove cloud-init too:
root@xxxx:/home/debian# apt purge ifupdown
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
cloud-init* ifenslave* ifupdown*
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 2094 kB disk space will be freed.
Hi Dan,
the mentioned out of the box debian 10 image does indeed have ifupdown installed. after the initial boot i see ifupdown tools available and systemd-networkd is available too, but the service is disabled. unfortunately removing ifupdown wont realy help as it would remove cloud-init too:
root@xxxx: /home/debian# apt purge ifupdown
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
cloud-init* ifenslave* ifupdown*
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 2094 kB disk space will be freed.
note this is on a freshly installed vm with the following image: https:/ /cdimage. debian. org/cdimage/ openstack/ current- 10/
any idea what's going wrong with:
a) the boot process
b) the package dependencies?