Memory limit quite low

[nalt]

The php memory_limit is not set and thus defaults to 128M. This results in a crash, when I try to generate thumbnails of photos taken with a standard digital camera usingocc preview:generate-all.

A larger memory limit is required for this standard task. It should be ok to increase it on installations that target only small groups of users.

Possible solutions:

• Explicitly set (a larger) memory_limit in Dockerfile
• Allow to set the memory limit with an ENV var
• Add a php-override.ini and document how to use it. Advantage: This would allow for all kinds of custom tweaks to php.ini

[Zogg]

Bump. Having the same issue.

[Svarto]

Hi, I have similar errors being thrown in my nextcloud install, any updates / working solutions to this?

[pierreozoux]

What should be the limit in your opinion?

[jkaberg]

@pierreozoux make it optional with a default (docker ENV) option?

[pierreozoux]

Does anybody want to PR this?

[monreal]

What would be the best workaround until this is implemented? I would like to set it to 512MB

[FriedCircuits]

@monreal I used Ansible to update the .htaccess file inside the docker from 512M to 2G after the docker is deployed. Looks like the default is now 512M.

[monreal]

@FriedCircuits for me it is still 128mb with 14rc. Do I have to change it manually in Nextcloud's .htaccess because it was not updated manually? Also I wonder why there is no php.ini at all

[monreal]

So, I actually got memory_limit=512M in my .user.ini
I guess occ does not get its setting from there? I noticed when I had to manually create some DB indices after the NC14 upgrade. The occ command worked but printed a warning about the setting being lower than the recommended 512mb. PHP default seems to be 128mb so without a php.ini I guess it is using that...

[ptrunk]

I am using the fpm-alpine image so i am not sure if it works for all images.

Because both php-cli and php-fpm support variable substitions i would suggest to use a custom /usr/local/etc/php/conf.d/nextcloud.ini with variables which should be changeable by the user. This file could be installed by the Dockerfile.

For Example

nextcloud.ini

memory_limit=${PHP_MEMORY_LIMIT}

Dockerfile

[...]
ENV PHP_MEMORY_LIMIT=512M
COPY nextcloud.ini /usr/local/etc/php/conf.d/nextcloud.ini
[...]

Now the user can run this image with -e PHP_MEMORY_LIMIT=1G and increase the limit.

[FriedCircuits]

@ptrunk That would be great and would work better with docker swarm since the container can be rebuilt at anytime. I hope someone at nextcloud can resolve this as it coming up on a year.

[ptrunk]

The php cli memory_limit problem is apparently fixed now by #460 but i am not sure a hardcoded value of 512M is the way to go because it still could be too low in some cases.

If someone wants to try i have created a custom docker image based on nextcloud:14.0.0-fpm-alpine with an environment variable PHP_MEMORY_LIMIT [1].

docker pull registry.gitlab.com/p7k/docker-nextcloud/nextcloud-fpm:14.0.0-1

I would prefer to have this kind of configuration also for other variables instead of using a .user.ini file but this is just my personal opinion.

[1] https://gitlab.com/p7k/docker-nextcloud/tree/master/fpm

[FriedCircuits]

@ptrunk Cool, I may it give it a try. I never could get the FPM to work with nginx/docker-proxy but now I am migrating to traefik so maybe it will work.

In my case 512M isn't enough. I need at least 1G. I can't remember why I was hitting the limit. I have external mounts and elasticsearch setup.

[gladiac]

Hello everybody,
so, the nextcloud docker-image comes by default with a .user.ini inside the document-root of nextcloud which already has 512M configured. However, just running

docker exec --user 33 -ti nextcloud occ preview:generate-all

is not enough to make use of it - it instead still falls back to the 128M that PHP considers to be default. To actually use .user.ini I came up with the following solution:

docker exec --user 33 -ti nextcloud php -c .user.ini -f occ preview:generate-all

This runs occ inside the container (in my case "nextcloud") as user 33 (which is www-data) but does it in a way so that PHP loads the configuration from .user.ini before. This way, you can configure whatever PHP option you want and it even is persistent if you made /var/www/html a docker-volume.
Hope that helps.
cheers, chris