#2961·devbox

Write process-compose logs to .devbox/process-compose.log, not /tmp

Author: jefftCreated Aug 28, 2026Updated Aug 28, 2026
Labelsfeaturetriage

What problem are you trying to solve?

I have a PHP app I use Devbox to construct a local development environment for (https://jefft.github.io/jethro-pmm/docs/2.40.0-dev/developer/DEVELOPMENT_DEVBOX). My process-compose.yml has mariadb, nginx, php-fpm and sundry init scripts all interdependent. When a service failed to start, I found it really hard to understand what process-compose is doing.

That is, until I stumbled upon the missing log file in /tmp, process-compose-$USER.log. This is generated by process-compose, which devbox wraps, and contains invaluable information on what process-compose is doing.

What solution would you like?

I suggest process-compose logs be written to .devbox/process-compose.log, alongside the existing compose.log.

Currently devbox invokes process-compose without a --log-file arg. process-compose therefore uses /tmp/process-compose-$USER.log as its fallback.

Alternatives you've considered

No response