Docker - Change php memory limit has no effect

[antoniotvr]

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues

Version

11.0.2

Bug description

Hi.

I have followed this documentation and I have glpi up and running through docker:

https://help.glpi-project.org/tutorials/procedures/running_glpi_on_docker

I need to increase php memory limit and so I have created the ini file as indicated and mapped the file to be used in the container.

I have indicated the new memory limit with this syntax that is correct:

memory_limit = 512M

But when I restart the container the php memory limit is not applied in the right way.

If I enter inside the container the custom config file hasn't the right value that I have configured.

Can you help me?

Thanks

Relevant log output

Page URL

No response

Steps To reproduce

• Create custom config file "custom-config.ini"
• Configure memory limit "memory_limit = 512M"
• start the container
• the memory limit indicated in glpi Home --> Setup --> General --> Performance is not correct (is the default, 128M).

Your GLPI setup information

No response

Anything else?

No response

[vboucard]

how do you start your container ?

[antoniotvr]

Hi.

I am using a docker compose file similar of that one indicated in the official documentation.

Other than the volume of glpi data I have added another line for the volume necessary to pass the custom php ini file (as indicated in the documentation).

Thank you

[vboucard]

i just tested it with podman on an fedora, it works

there may be an error though in the documentation, it's "ro" and not "r" (as in https://docs.docker.com/reference/compose-file/services/#short-syntax-5)

if you ls -l /usr/local/etc/php/conf.d/ in your container do you see the custom file (and with correct perms) ?

then you can check the setting with php -r "phpinfo();"|grep memory_limit

[antoniotvr]

Hi. Thank you! I will try to change the compose file indicating ro instead r. Until now if I enter the container I cannot see my custom file with the right content so maybe the problem is this wrong configuration that cause the issue. If the container is already created is sufficient to restart or there is the need to remove it and recreate it? Thanks Il ven 7 nov 2025, 17:20 vboucard ***@***.***> ha scritto:

…

*vboucard* left a comment (glpi-project/docker-images#221) <#221 (comment)> i just tested it with podman on an fedora, it works there may be an error though in the documentation, it's "ro" and not "r" (as in https://docs.docker.com/reference/compose-file/services/#short-syntax-5) if you ls -l /usr/local/etc/php/conf.d/ in your container do you see the custom file (and with correct perms) ? then you can check the setting with php -r "phpinfo();"|grep memory_limit — Reply to this email directly, view it on GitHub <#221 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADSEWAHR2M6TQE5H7DOAOM333TBDPAVCNFSM6AAAAACLKLZYLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMBTGQ4DCNJXG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[vboucard]

just a restart afetr making the change in the compose file should do it

[antoniotvr]

Hi.

I have done the modification in docker compose file (added ro instead r in the volume of custom config ini).

I have restarted containers but the problem is still the same.

I have entered the glpi container and this is the content of custom php config file:

cat /usr/local/etc/php/conf.d/custom-config.ini
memory_limit = 1024M

So the file has the modified parameter.

But in the web ui of glpi I see this:

So the memory parameter is the default one.

Thank you for your help

[vboucard]

I think your are looking at the wrong place.

the screenshot indicates the memory limit for the opcache (not sure what it is)

you have to look in setup->general, system tab (just 2 tabs over performance, where you was), server panel

and also the command php -r "phpinfo();"|grep memory_limit should return the expected value

[antoniotvr]

Hi. I will check it and let you know. Thank you for your precious help. Il ven 14 nov 2025, 10:27 vboucard ***@***.***> ha scritto:

…

*vboucard* left a comment (glpi-project/docker-images#221) <#221 (comment)> I think your are looking at the wrong place. the screenshot indicates the memory limit for the opcache (not sure what it is) you have to look in setup->general, system tab (just 2 tabs over performance, where you was), server panel image.png (view on web) <https://github.com/user-attachments/assets/2e15ab9c-4f48-496f-8317-6b4e5ea51bbe> and also the command php -r "phpinfo();"|grep memory_limit should return the expected value — Reply to this email directly, view it on GitHub <#221 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADSEWAE3DF3HCGPEL42TWWD34WN65AVCNFSM6AAAAACLKLZYLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMZRG44DCMJZGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[antoniotvr]

Hi.

I have checked and you are right, parameter of max memory is correct.

Anyway with your help is working because I have checked and without "ro" for the volume parameter inside the docker compose file the custom ini file is not corrected configured for the container.

Thank you