Non-interactive installation

[Zelnes]

My goal is to be able to set environment variables and then call one script (for example https://github.com/community-scripts/ProxmoxVE/blob/main/ct/prometheus-pve-exporter.sh).

I read build.func documentation and source code, and it seems that there are some errors in the doc.
For example, this part suggests to set CTID variable, which leads to an error, because the code actually expects CT_ID.

Also, it says here that you can set variables and create containers by just source-ing the build.func.
This does nothing, just declares some functions.

My question is: despite every places where it says « This can be possible, depending on the script called » (like here), is it really possible ?
And if yes, how ?

I have tried many ways.

The doc says that start should be the entrypoint, but this always opens the TUI for selection, even when I declare many variables.
And if I call build_container, it fails, and I think that this is because some variables might be missing even if they are declared as var_*.

Here's an example

Details

# cat test.sh 
#!/usr/bin/env bash

export APP=test
export CT_ID="356"
export var_hostname="${APP}-server"
export var_os="debian"
export var_version="13"
export var_cpu="2"
export var_ram="2048"
export var_disk="10"
export var_net="vmbr0"
export var_gateway="192.168.1.1"
export var_ip="192.168.1.2"
export var_template_storage="local"
export var_container_storage="local"
export ENABLE_FUSE="true"
export ENABLE_TUN="true"
export SSH="true"
source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/build.func)

# start -> Open the TUI

build_container
install

When I execute the above script (start in comment), I have

bash test.sh
  ✔️   Storage space validated
  ✔️   Storage local (Free: 153.4GB  Used: 55.4GB) [Template]
  ✔️   Storage local (Free: 153.4GB  Used: 55.4GB) [Container]
  ✔️   Storage 'local' (dir) validated
  ✔️   Template storage 'local' validated
  ✔️   Template search completed
  ✔️   Template debian-13-standard_13.1-2_amd64.tar.zst [local]
  ✖️   Container creation failed. See /tmp/pct_create_356_20260317_153847_.log
+ pct create 356 local:vztmpl/debian-13-standard_13.1-2_amd64.tar.zst -features nesting=1 -hostname -net0 name=eth0,bridge=vmbr0,ip=dhcp -onboot 1 -cores -memory -unprivileged -rootfs local:8
+ tee -a /tmp/pct_create_356_20260317_153847_.log
400 too many arguments
pct create <vmid> <ostemplate> [OPTIONS]
+ set +x

We can see that hostname cores memory or unprivileged are missing their values, even if I declared them (I used the same variable declaration as in the create_container function from the documentation).

[MickLesk]

var_CTID or CTID is the correct

[Zelnes]

Thank you for your answer, however I can't find any reference to var_CTID. The only reference is to var_ctid here

ProxmoxVE/docs/misc/build.func/BUILD_FUNC_ADVANCED_SETTINGS.md

Line 20 in 4aa83fd

| 3 | Container ID | `var_ctid` | Unique container ID (auto-suggested) |

But this seems to be related to the wizard.

I have tried the documented way

ProxmoxVE/docs/misc/build.func/BUILD_FUNC_ADVANCED_SETTINGS.md

Lines 140 to 155 in 4aa83fd

	### Non-Interactive with All Options
	```bash
	# Set all variables for fully automated deployment
	export var_unprivileged=1
	export var_cpu=2
	export var_ram=2048
	export var_disk=8
	export var_net=dhcp
	export var_fuse=no
	export var_tun=no
	export var_gpu=yes
	export var_nesting=1
	export var_protection=no
	export var_verbose=no
	bash -c "$(curl -fsSL https://...jellyfin.sh)"

But it doesn't work better.
Do I miss anything in my setup ?

test-jellyfin.sh

#!/usr/bin/env bash

export var_unprivileged=1
export var_cpu=2
export var_ram=2048
export var_disk=8
export var_net=dhcp
export var_fuse=no
export var_tun=no
export var_gpu=yes
export var_nesting=1
export var_protection=no
export var_verbose=no

bash -c "$(curl -fsSL **https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyfin.sh)"**

Which still opens the TUI, when the doc explicitly says

Set all variables for fully automated deployment

In my post I said multiple things, about source-ing the build.func that is said to be enough to build a container, about the multiple places where the documentation is explaining some ways to perform non-interactive installation.
Do you have any clue on how should I interpret this, or if there are any errors ?

[MickLesk]

Did you Test this?

https://community-scripts.org/generator

[Zelnes]

Actually no, I'll give it a try.

It work well, thanks 👍

I think the documentation may only miss the mode=generated then

[MickLesk]

Yeah the Docs atm outdated and will be integrated into new Frontend in next time