Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/etc/network/interfaces not imported from template #1088

Closed
andreas-grimm opened this issue Aug 31, 2024 · 2 comments
Closed

/etc/network/interfaces not imported from template #1088

andreas-grimm opened this issue Aug 31, 2024 · 2 comments
Labels

Comments

@andreas-grimm
Copy link

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

Copy link

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

@github-actions github-actions bot added the stale label Oct 30, 2024
Copy link

github-actions bot commented Nov 4, 2024

This issue was closed because it has been inactive for 5 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant