Closed antfig closed 9 months ago
Hi @antfig,
I think supervisor isn't suitable to run on a readonly filesystem, it needs at least a temporary directory to create the logfiles.
You can mount specific folders to tmpfs using --mount type=tmpfs,destination=/tmp
.
That solves the issue with supervisor, but then you get errors from nginx & php-fpm because they want to create a pid file and logfiles as well.
Those issues are solveable by changing the paths in the various configuration files.
Thanks for the help :)
Hi, first of all, thanks for the nice work with this simple docker image.
I'm doing some tests running this container in a read-only system and I got some errors from the supervisor trying to access
/tmp
directory, from the supervisor settings looks like everything is sent to thestdout
orstderr
but still has the error.How to reproduce
By running the docker in read-only mode
Run the following
Research
From the supervisor codebase (here), I can see the error is originated from setting the
childlogdir
configuration that has a default to tmp dir.I tried to set the
childlogdir=/dev/null
but failed because /dev/null is not an existing directory