[pve-devel] applied: [PATCH container] config: allow empty environment variables
Thomas Lamprecht
t.lamprecht at proxmox.com
Mon Nov 17 15:15:45 CET 2025
On Mon, 17 Nov 2025 13:49:03 +0100, Filip Schauer wrote:
> This fixes a problem with the docker.io/httpd OCI image which specifies
> an empty environment variable. This violated the pattern of the `env`
> property, causing `pct config <vmid>` to fail with:
> ```
> env: value does not match the regex pattern
> ```
>
> [...]
I actually wondered about that and had the frontend "allowBlank" check
initially such that the value was only required if the name field was set (as
the variable simply gets deleted otherwise), but I then changed it to both to
be required, as allowing something more is almost always easier to do in the
future compared to restricting it, especially if it involves API exposed schema.
Anyhow, the UI part would need now also adaption to make your change fully work
also there.
Applied, thanks!
[1/1] config: allow empty environment variables
commit: 9a5f5ce5cfdbc85b2d40a4a20662065d18b85f6c
More information about the pve-devel
mailing list