You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, I override the www.conf with my customized FPM pool config which contains a "listen = /run/php/php.sock". When the container started there was no socket. After several minutes I found the mistake in file /usr/local/etc/php-fpm.d/zz-docker.conf. It redefines the "www" pool listen setting to tcp. Contents of the file:
[global]
daemonize = no
[www]
listen = 9000
Why this file exists? Why is it needed to contain "listen = 9000"?
The text was updated successfully, but these errors were encountered:
I'd like to use the php-fpm container with socket listener(more secure I think) instead of tcp. I run my instance like this:
So, I override the www.conf with my customized FPM pool config which contains a "listen = /run/php/php.sock". When the container started there was no socket. After several minutes I found the mistake in file /usr/local/etc/php-fpm.d/zz-docker.conf. It redefines the "www" pool listen setting to tcp. Contents of the file:
Why this file exists? Why is it needed to contain "listen = 9000"?
The text was updated successfully, but these errors were encountered: