PHP ini settings not applied when command provided

[Thijmen]

So, here's the case.
I build 1 docker image for web and my job runner.
The web instance runs fine and my environment variables gets applied to PHP ini config just fine.

However, in Kubernetes, when I start the container with a command (eg php craft queue/listen), it seems that no settings get applied.

Is there a way to force this? Do I have to run a command before running my command, to apply the settings from ENV to php ini config?

I use shinsenter/php:8.2-fpm-apache by the way. Should I use cli for the CLI one?

[Thijmen]

I think I got it working by putting my run command in the SUPERVISOR_PHP_COMMAND env variable. Is this the way to go?

[shinsenter]

@Thijmen

Thank you for reaching out regarding an issue related to the Docker images I provided.

It seems the problem you’re encountering is due to calling the PHP binary directly before the container has a chance to initialize the appropriate configuration files during the bootstrap phase. In this case, PHP will run with its default configuration, just as it does in the official PHP Docker images by default.

If you’re using the shinsenter/php:8.2-fpm-apache image, I’d appreciate it if you could help by running the following commands. This will give me more accurate information about your environment and the binary being executed:

• which php
• bash -c 'echo $PATH'

Once you provide these details, I’ll continue investigating the root cause of the issue.

Regarding the use of the SUPERVISOR_PHP_COMMAND environment variable for executing a command, before executing the your command, the container will initialize the necessary environment and configuration for PHP to run - just as intended. In that case, please note that the container will replace its main process (Apache + PHP-FPM) with the command you define in SUPERVISOR_PHP_COMMAND.

[shinsenter]

By the way, if your php craft queue/listen command is a long-lived process, you can treat it as the main process running inside its own container. In this case, it can replace the default Apache + PHP-FPM process. Using the SUPERVISOR_PHP_COMMAND environment variable in this case aligns perfectly with the design I originally intended.