🚀 Looking for Testers – New Config Files Feature!

[michelroegl-brunner]

Hi everyone

We're looking for testers to try out our new config files feature! If you're interested in getting early access and helping us improve it, we'd love your feedback.

How to test

We have created a test branch for this feature so we do not disturb productive use of our scripts. Keep in mind that this test branch may not include latest bug fixes or improvements.
Do not use this for productive systems.
This is only for development testing and feedback. You can install the scripts as you are used to. There is no support for alpine at the moment. Please report all errors you encounter or feedback you have as answer to this thread, not as a new issue or disscusion please. This will get closed immediately. There is no support when using this scripts besides problems with the config files.

Bash command to start LXC install.

Use the following command
bash -c "$(wget -qLO - https://raw.githubusercontent.com/community-scripts/ProxmoxVE/config_file/ct/APPLICATION.sh)"
and change APPLICATION.sh with your desired app (debian.sh for example).

After starting the script use point 4 Use Config File

###Config file

You need to create a file on your PVE Host to supply the configs befor running the scripts. It is defined by us to be /opt/community-scripts/.settings but you can change that in the prompt to whatever you wish.

If all or some settings are not present in the file, default values get used.

What settings are available?

The following settings can be provided with this file at the moment (subject to changes).

Caution

There is some input sanity checking missing, if wrong values are entered the script may break

Name	Value
CT_ID	ID for LXC,can be a single number or a range 100-9999
var_os	debian or ubuntu
var_version	11 or 12 for Debian 20.04, 22.04, 24.04, 24.10 for Ubuntu
CT_TYPE	1 unprivileged or 0 privileged
PW	password for root
HN	hostname of the container
DISK_SIZE	size of the disk in GB
CORE_COUNT	number of cores
RAM_SIZE	size of ram in MiB
BRG	Name of the bridge (vmbr0)
NET	IP-Address/CIDR (192.168.0.1/24)
GATE	Gateway Address (192.168.0.254)
APT_CACHER_IP	Ip Addresse of APT-Cacher (192.168.0.2)
DISABLEIP6	yes or no
MTU	'1500'
SD	Search domain (example.com)
NS	IP of Nameserver (192.168.0.100)
MAC	Mac address of device
VLAN	VLAN ID (100)
TAGS	Custom Tags
SSH	yes or no
SSH_AUTHORIZED_KEY	SSH Key
VERB	yes or no

Example file

Each value needs to be in double qoutes.

DISK_SIZE="25"
CORE_COUNT="33"
RAM_SIZE="4500"
HN="TEST"
BRG="vmbr1"
NET="10.10.10.171/24"
GATE="10.10.10.254"
VLAN="100"
SSH="yes"
TAGS="dev;testing"
SSH_AUTHORIZED_KEY="REDACTED"

[mon5termatt]

Can DHCP be an option?

[michelroegl-brunner]

Dhcp is the default. If you dont set a ip address in the config file, dhcp is used.

[mon5termatt]

cool. i have a few changes i want to make to each machine and that makes it easier if it asks if not provided via file.

[mon5termatt]

Sorry for the formatting, its being dumb, Im having some small issues when providing the gateway but not the IP. i want it to grab a dhcp lease in the VLAN 2 Range of 10.2.0.0/24

BRG="vmbr0"
GATE="10.2.0.1"
VLAN="2"
SSH="yes"
TAGS="dev;testing"
PW="REDACTED"

💡 Using Config File on node pve
💡 Using config File: /root/.settings
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
🔐 Root Password: ********
🆔 Container ID: 100
🏠 Hostname: dockge
💾 Disk Size: 18 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🌉 Bridge: vmbr0
📡 IP Address: DHCP
🌐 Gateway IP Address: Default
🚫 Disable IPv6: No
⚙️ Interface MTU Size: 1500
🔍 DNS Search Domain: HOST
📡 DNS Server IP Address: HOST
🏷️ Vlan: 2
📡 Tags: dev;testing
🔑 Root SSH Access: yes
🔑 SSH Authorized Key: None
🔍 Verbose Mode: No
🚀 Creating a Dockge LXC using the above settings
✔️ Using local for Template Storage.
✔️ Using local-lvm for Container Storage.
✔️ Updated LXC Template List

⠼400 Parameter verification failed.
net0: invalid format - format error
net0.ip: invalid format - value does not look like a valid ipv4 network configuration

pct create <vmid> <ostemplate> [OPTIONS]
bash: line 201: exit: A problem occured while trying to create container.: numeric argument required

[mon5termatt]

I have a error in the script, i fix that tomorrow. But why would you want to spezifiy the GW when DHCP. I have a strong Network engineering background, and this makes no sense for me^^

Just skips me a step. I have everything on that vlan (2) with the GW of 10.(2).0.1, but I would still want to specify the IP

[michelroegl-brunner]

But you get the correct gateway with dhcp anyways? I dont see the benfit tbh.
And proxmox dont allows dhcp + gatway as per my testing.

[michelroegl-brunner]

nevermind, it is working now as you wanted.

[mon5termatt]

But you get the correct gateway with dhcp anyways? I dont see the benfit tbh. And proxmox dont allows dhcp + gatway as per my testing.

i was not aware of that.

[michelroegl-brunner]

But you get the correct gateway with dhcp anyways? I dont see the benfit tbh. And proxmox dont allows dhcp + gatway as per my testing.

i was not aware of that.

Nah, this was a bug? on my node, it worked after a few trys.

[mon5termatt]

Just an idea but only prefill and skip the options that are defined in the file and still prompt for the others.

[mon5termatt]

So example...

Script= read from script.

ID="200-299" SPECIFY RANGE FOR ID, IF 200 IS TAKEN USE 201 ETC.

DISK_SIZE="SCRIPT"
CORE_COUNT="SCRIPT"
RAM_SIZE="SCRIPT"
HN="SCRIPT"

BRG="vmbr0"
NET="DHCP"
GATE="10.2.0.1"

[michelroegl-brunner]

I will have a look at this an see what i can take from your feedback.
The id i dont see why you would ever set that manually, i would just leave this as automatic.
The Ip Range i have to see if this is possible somehow, but i dont think so.

[LilTrublMakr]

I could see ranges helpful for people that use dev/staging/prod containers. e.g. if the dev is in range 300-399, staging is in 200-299, and prod in 100-199. It could be helpful if someone uses multiple ENV (or settings in this case) files for those that have a setup like this.

As for IP address: in my instance, I use the machine ID as the last octet of the IP address. e.g. if the machine ID is 111, the IP would be 192.168.12.111/24 with a vlan tag. Though this may or may not be a common practice, it does work well and make things slightly easier to manage.

[mon5termatt]

Yeah I use a similar scheme.

If it has the ID of 211 its 10.2.0.11 (VLAN 2)

If the ID is 305 its 10.3.0.5 (VLAN 3)

[michelroegl-brunner]

ID Ranges are implemented. you can use CT_ID="100-200" for example. It checks for the next available ID.

[alexanderjerome]

Hey! I'm really glad to see this feature being tested, I'm happy to test it.

A couple of ideas that came to me when I read the initial post:

1. Post installation scripts - user can define commands to run afterwards. There could be a dedicated directory for post-install scripts to use, i.e. logging the root password to Vaultwarden, automating GPU passthrough, installing Tailscale / Netbird, bind mounting directories with proper permissions, etc. The user can provide their own scripts for this.

This feature can also piggy back onto @LilTrublMakr 's comment about ip addressing - I have the exact same practice, but instead of modifying the configuration script to handle this, the user could run their own custom script to update the LXC / VM settings to their preferences.

2. Settings / config files should be distinguished by script being run. It could be possible, for the user to contain configuration files for each individual automation script, so they can create a repeatable template that is specific to the service being installed. This way, should the user need to recreate their service, its quicker to reproduce and automate. The configuration file can then override the customization variables in the original build function, and possibly given a flag (-y to accept values on config file and complete the installation without interaction).

Above all, thanks for keeping ttecks legacy alive and well. It seems like every other day a new script appears in the repo, so kudos to the maintainers!

[michelroegl-brunner]

1.) To be fair, this i think would get messy really quick, i have to think about that.

2.) you can set the name of the file during the dialouge, you can to that as you described. I dont think most user would create a file for each script the run? but i can add a check for that (If debian.conf in /opt/community-scripts/ is present use it by deafult, otherwise use the default one). About automation: we have decided we will not implement this due to security concerns.

[michelroegl-brunner]

number 2 was rather easy, is implemented.

[LilTrublMakr]

About automation: we have decided we will not implement this due to security concerns.

That is actually kind of disappointing to see but understandable from a security standpoint. I was thinking about suggesting this today because it would make some of my tasks easier. Right now, I manually set up a container, add it to Netbox, add info to an Ansible playbook, and add it to Uptime Kuma. It would be very nice if I was able to automate all of this when a container is created. I suppose that this could still be done from a manual run of a script though...