Closed pdf closed 4 months ago
I haven't seen this one before and I just checked that I was still seeing stderr logs on a running container. I'm a few minor versions behind, so it's certainly possible this is new. Since you are running Laravel, are using something like supervisord? I suspect if you are, this is eating your stderr logs.
No supervisor - we have separate containers for web and background tasks.
I have just written a minimal repro though (since index.php that writes to stderr), and I can see output from that, so must be something related to how Laravel is operating, will dig in further to try to find the culprit in the app code.
Apologies for the noise.
What happened?
I'm running a Laravel application in non-worker mode and have configured monolog to stream output to
php://stderr
, however logs do not appear on the container stderr handle. I do get Caddy logs if I configure the vhost to output access logs to stderr, and I did have application logs under apache/mod_php.I can see that PHP CLI stdin/out/err are wired up explicitly, and I see what I presume the SAPI log interface registered as
frankenphp_log_message
, but I couldn't find for php_server where PHP stderr would get connected to a logger or the host fd.Build Type
Docker (Debian Bookworm)
Worker Mode
No
Operating System
GNU/Linux
CPU Architecture
x86_64
PHP configuration
Relevant log output
No response