-
Notifications
You must be signed in to change notification settings - Fork 984
Description
Environment
Nextcloud AIO 33
Docker
Proxmox VM
PHP 8.3
Container: nextcloud-aio-nextcloud
Problem
The variable NEXTCLOUD_MEMORY_LIMIT is documented in the code but appears to have no effect on the Nextcloud container.
ConfigurationManager.php reads:
getEnvironmentalVariableOrConfig('NEXTCLOUD_MEMORY_LIMIT', 'nextcloud_memory_limit', '512M');
However the value is never injected into the container environment.
Observed behavior
nextcloud-aio-nextcloud is always started with:
PHP_MEMORY_LIMIT=512M
Even when the mastercontainer is started with:
-e NEXTCLOUD_MEMORY_LIMIT=1024M
Verification
docker inspect nextcloud-aio-nextcloud | grep PHP_MEMORY_LIMIT
always shows:
PHP_MEMORY_LIMIT=512M
Also NEXTCLOUD_MEMORY_LIMIT is not present in the container environment.
Root cause (likely)
There is no placeholder for %NEXTCLOUD_MEMORY_LIMIT% in the container environment template used to build nextcloud-aio-nextcloud.
Therefore the configuration value is never propagated.
Expected behavior
NEXTCLOUD_MEMORY_LIMIT should set PHP_MEMORY_LIMIT in the nextcloud container.
Example expected result:
PHP_MEMORY_LIMIT=1024M