PHP-FPM Configuration in Docker Compose '/usr/local/etc/php-fpm.d/zz-generated-settings.conf': No such file or directory (2)

[hhaswan]

I have configured the docker-compose.yml (using shinsenter/php:7.1-fpm-nginx) with the following environment variables:

environment:
  - TZ=Asia/Makassar
  - DOCUMENT_ROOT=/app
  - ALLOW_RUNTIME_PHP_ENVVARS=1
  - PHP_MAX_EXECUTION_TIME=1800
  - PHP_POST_MAX_SIZE=100M
  - PHP_UPLOAD_MAX_FILESIZE=100M
  - PHP_MAX_INPUT_TIME=600
  - PHP_MAX_INPUT_VARS=3000
  - PHP_REQUEST_TERMINATE_TIMEOUT=1800

However, when running docker compose logs -f, I encounter the following error:

app-3  | [12-Mar-2025 00:30:08] ERROR: failed to open configuration file '/usr/local/etc/php-fpm.d/zz-generated-settings.conf': No such file or directory (2)
app-3  | [12-Mar-2025 00:30:13] ERROR: failed to load configuration file '/usr/local/etc/php-fpm.d/zz-generated-settings.conf'

This error occurs after adding PHP_REQUEST_TERMINATE_TIMEOUT=1800. I would like to adjust PHP-FPM for the request_terminate_timeout variable. Any assistance would be appreciated.

[shinsenter]

Hi @hhaswan

I’ve reviewed your setup and tried using the following docker-compose.yml to create a container, and I didn’t notice anything unusual.

services:
  test:
    image: shinsenter/php:7.1-fpm-nginx
    ports:
      - 80:80
    environment:
      - TZ=Asia/Makassar
      - DOCUMENT_ROOT=/app
      - ALLOW_RUNTIME_PHP_ENVVARS=1
      - PHP_MAX_EXECUTION_TIME=1800
      - PHP_POST_MAX_SIZE=100M
      - PHP_UPLOAD_MAX_FILESIZE=100M
      - PHP_MAX_INPUT_TIME=600
      - PHP_MAX_INPUT_VARS=3000
      - PHP_REQUEST_TERMINATE_TIMEOUT=1800

Could you provide any additional information that you think might be relevant?

[JAGulin]

Maybe this is stale and to be closed, but adding some ideas for future visitors.

app-3 | [12-Mar-2025 00:30:08] ERROR: failed to open configuration file '/usr/local/etc/php-fpm.d/zz-generated-settings.conf': No such file or directory (2)

You should look if the file is available on the docker and who owns it. I've only tried apache, but in my case it's generated when "compose up".

ls -la /usr/local/etc/php-fpm.d/
total 72
drwxr-xr-x 1 root root  4096 May  1 09:09 .
drwxr-xr-x 1 root root  4096 Apr 11 17:02 ..
-rw-r--r-- 1 root root   428 Apr 11 17:02 docker.conf
-rw-r--r-- 1 root root 22133 Apr 11 17:02 www.conf
-rw-r--r-- 1 root root 22133 Apr 11 17:02 www.conf.default
-rw-r--r-- 1 root root    45 Apr 11 17:02 zz-docker.conf
-rw-r--r-- 1 root root   910 May  1 09:09 zz-generated-settings.conf

I believe php-envvars will write the file. If you set DEBUG_MODE=1 maybe you can get more info.
https://github.com/shinsenter/php/blob/main/src/php/common/shell-php/php-envvars
Was it ever called or did it fail earlier, for some other reason?

You can also run these commands to see what they say.
env-default |& less
php-envvars dump

This error occurs after adding PHP_REQUEST_TERMINATE_TIMEOUT=1800.

So you had it working before that? Can you revert back and see what the file said then?
Try then adding the line "by hand" so that you're sure not to copy-paste any invisible or incompatibe characters.

I would like to adjust PHP-FPM for the request_terminate_timeout variable. Any assistance would be appreciated.

As a workaround you should be able to do this directly in a *.conf file. In many cases, I'd say that could be an easier way than the environment variables in many cases. Just mount your own conf in compose yml.

volumes:
  - /srv/www/zzz_fpm_php.conf:/usr/local/etc/php-fpm.d/zzz_fpm_php.conf # php conf

Note the zzz to override the zz if needed.

• ALLOW_RUNTIME_PHP_ENVVARS=1

I don't know if you need or use this, but it might allow setting the variable in runtime too.

---

@shinsenter A bit off topic, but I got curious when I read the code.
When I tried to run the env-default below on command-line it seems to do nothing.

    run("env-default '# Environment variables for PHP'");

https://github.com/shinsenter/php/blob/7201438190b32db46da34fe783a0af4651f039bd/src/php/common/shell-php/php-envvars#L136C1-L136C62

Was the inner 'ticks' intentional? And why is it there at all? It doesn't populate nor clear "all_env_vars" does it? Am I missing something?

[shinsenter]

@JAGulin Thank you for your kindness explanation.

When I tried to run the env-default below on command-line it seems to do nothing.

↑
If a parameter for the env-default command starts with #, it will add a comment line to the target config file. In this case, it will output the exact string # Environment variables for PHP into the /etc/.docker-env file.

php/src/php/common/rootfs/usr/local/bin/env-default

Lines 34 to 37 in 7201438

	if [ "${line:0:1}" = "#" ]; then
	echo -e "\n${line}\n# ------------------------------------------------------------ #" >>$conf_path
	exit
	fi

I do this to make it easier to review generated config files, as having comments improves readability.

[JAGulin]

As for the original bug-report (and the 201), I think it can be closed. But it might be useful to keep it visible as a FAQ, if you have some way to do so.

As for my off-topic question, that's also closed:

it will output the exact string # Environment variables for PHP into the /etc/.docker-env file.

I see, so functionally "do nothing" was the expected result even though I didn't expect env-default to do that. Thank you for the clarification, maybe there should be an additional comment saying "# add comment to .docker-env" to further improve readability. :-)