You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When generating a new VM using 3.0.1-rc1 and a Debian 12 template, a modified /etc/network/interface file gets overwritten with the original Debian network configuration file:
The template is holding a configuration file using a static network address, eg. 192.168.0.56. So the file in the templates looks like:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug ens18
iface ens18 inet static
address 192.168.0.56
netmask 255.255.255.0
gateway 192.168.0.1
But after the generation of the new VM, the network file is back to the Debian original:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug ens18
iface ens18 inet dhcp
Using the Proxmox GUI, the new generated VM hold the file of the template.
Workaround:
I am using rc.local to update the configuration after generation during the first start-up
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open for 60 days with no activity. Please update the provider to the latest version and, in the issue persist, provide full configuration and debug logs
When generating a new VM using 3.0.1-rc1 and a Debian 12 template, a modified /etc/network/interface file gets overwritten with the original Debian network configuration file:
The template is holding a configuration file using a static network address, eg. 192.168.0.56. So the file in the templates looks like:
But after the generation of the new VM, the network file is back to the Debian original:
Using the Proxmox GUI, the new generated VM hold the file of the template.
Workaround:
I am using
rc.local
to update the configuration after generation during the first start-upThe text was updated successfully, but these errors were encountered: