ALERT: [pool www] user has not been defined

[michalhlavka]

Hi, I am starting container from FROM thecodingmachine/php:7.4-v3-fpm and getting

php_1       | [07-Jul-2020 13:22:56] ALERT: [pool www] user has not been defined
php_1       | [07-Jul-2020 13:22:56] ALERT: [pool www] user has not been defined
php_1       | [07-Jul-2020 13:22:56] ERROR: failed to post process the configuration
php_1       | [07-Jul-2020 13:22:56] ERROR: failed to post process the configuration
php_1       | [07-Jul-2020 13:22:56] ERROR: FPM initialization failed
php_1       | [07-Jul-2020 13:22:56] ERROR: FPM initialization failed

At the local machine, everything is right but on the server, it's failing.

Distributor ID:	Debian
Description:	Debian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

4.19.0-9-amd64

Any advice? One week I am trying to figure it out, what is wrong. Thank you.

[DepkaCZ]

The user is really not defined in /etc/php/7.4/fpm/pool.d/www.conf this also applies to 7.1 images as well please fix it.

Temporary solution is to get the /etc/php/7.4/fpm/pool.d/www.conf out of the container, modify it by uncommenting the user = www-data line and then overwrite it e.g. in docker compose

[DepkaCZ]

Hmm, my previous post is only partial solution as I'm getting error when trying to install new composer packages :

Cannot create cache directory /home/docker/.composer/cache/repo/https---repo.packagist.org/, or directory is not writable. Proceeding without cache

I've tried to change group/user to docker/docker as stated in readme but without any luck :/

[beejaz]

We have the same error since recently. Trying to load thecodingmachine/php:7.4-v3-slim-fpm on a fresh computer without previous installation/cache gives this:
php_1 | [01-Oct-2020 19:28:49] ALERT: [pool www] user has not been defined
php_1 | [01-Oct-2020 19:28:49] ALERT: [pool www] user has not been defined
php_1 | [01-Oct-2020 19:28:49] ERROR: failed to post process the configuration
php_1 | [01-Oct-2020 19:28:49] ERROR: failed to post process the configuration
php_1 | [01-Oct-2020 19:28:49] ERROR: FPM initialization failed
php_1 | [01-Oct-2020 19:28:49] ERROR: FPM initialization failed

[DepkaCZ]

I've solved it by disabling WSL support in Docker for windows

[beejaz]

Thats strange. I get this error on a Linux host that has nothing to do with Docker for Windows also.

[moufmouf]

Hey guys,

Could you explain me how to reproduce this problem (on a Linux host if possible)?

Because right now, I don't know how to generate this error.

$ docker run thecodingmachine/php:7.4-v3-fpm
[05-Oct-2020 08:17:27] NOTICE: fpm is running, pid 3338
[05-Oct-2020 08:17:27] NOTICE: ready to handle connections
[05-Oct-2020 08:17:27] NOTICE: systemd monitor interval set to 10000ms

I'm looking at a way to add a breaking test before trying to solve this issue.

[beejaz]

Hi @moufmouf

It worked on all my hosts that has previous cache (or something) from your image even if i choose --no-cache option. But when I use a fresh new VM with Linux (Ubuntu) it didnt work.

I tried to replicate this, again, today on a fresh machine and now it works for me. I will test on one of the old hosts that didnt work. Ill get back.

[michalhlavka]

With docker run thecodingmachine/php:7.4-v3-fpm everything it's ok.

But when I use docker-compose along with nginx, it's again

[06-Oct-2020 12:37:39] ALERT: [pool www] user has not been defined
php_1       | [06-Oct-2020 12:37:39] ALERT: [pool www] user has not been defined
php_1       | [06-Oct-2020 12:37:39] ERROR: failed to post process the configuration
php_1       | [06-Oct-2020 12:37:39] ERROR: failed to post process the configuration
php_1       | [06-Oct-2020 12:37:39] ERROR: FPM initialization failed
php_1       | [06-Oct-2020 12:37:39] ERROR: FPM initialization failed

docker-compose

services:
  nginx:
    build:
      context: .
      dockerfile: ./.docker/nginx/Dockerfile
    volumes:
      - ./:/var/www/html/
      - ./.docker/nginx/nginx.conf:/etc/nginx/nginx.conf
      - ./.docker/nginx/sites/:/etc/nginx/sites-available
      - ./.docker/nginx/conf.d/:/etc/nginx/conf.d
    depends_on:
      - php
    ports:
      - "80:80"
      - "443:443"
  php:
    build:
      context: .
      dockerfile: ./.docker/php/Dockerfile
    volumes:
      - ./:/var/www/html
    environment:
      PHP_EXTENSION_XDEBUG: 0
      PHP_EXTENSION_PGSQL: 1
      PHP_EXTENSION_PDO_PGSQL: 1
      PHP_EXTENSION_MYSQLI: 0
      STARTUP_COMMAND_1: chown docker /proc/self/fd/{1,2} // this should be fix, but it's not working

PHP Dockerfile

FROM thecodingmachine/php:7.4-v3-fpm

COPY ./ /var/www/html/

WORKDIR /var/www/html/

CMD ["php-fpm"]

EXPOSE 9000

Nginx Dockerfile

FROM nginx:alpine
COPY ./ /var/www/html/
CMD ["nginx"]

EXPOSE 80 443

[mbrowngold]

I've solved it by disabling WSL support in Docker for windows

This solved it for me as well.

[beejaz]

This started to work out of nowhere for me 👍 Both on Linux hosts and WSL2 host with docker for windows

[DepkaCZ]

Still not working for me :/

…

On Thu, Oct 15, 2020 at 8:20 PM Björn ***@***.***> wrote: This started to work out of nowhere for me 👍 Both on Linux hosts and WSL2 host with docker for windows — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#206 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAOTQVIJZ75I3O67EM3RXTSK44O5ANCNFSM4OS2GVZQ> .

[racinmat]

Happening to me too, windows 10, using WSL.

[DepkaCZ]

Arent you trying to run the docker compose from windows shell ? I found that you must run it from wsl shell čt 8. 4. 2021 v 19:14 odesílatel Matěj Račinský ***@***.***> napsal:

…

Happening to me too, windows 10, using WSL. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#206 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAOTQW75DN5HCNTDGZHVQLTHXP7TANCNFSM4OS2GVZQ> .

[racinmat]

Thanks, I'll try it. Unfortunately, running it from wsl shell causes me docker/compose#7899

[lordisp]

Arent you trying to run the docker compose from windows shell ? I found that you must run it from wsl shell

seams that did it. however the cause for this would be good to understand