-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ALERT: [pool www] user has not been defined #206
Comments
The user is really not defined in Temporary solution is to get the |
Hmm, my previous post is only partial solution as I'm getting error when trying to install new composer packages :
I've tried to change group/user to |
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: |
I've solved it by disabling WSL support in Docker for windows |
Thats strange. I get this error on a Linux host that has nothing to do with Docker for Windows also. |
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.
I'm looking at a way to add a breaking test before trying to solve this issue. |
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. |
With But when I use docker-compose along with nginx, it's again
docker-compose
PHP Dockerfile
Nginx Dockerfile
|
This solved it for me as well. |
This started to work out of nowhere for me 👍 Both on Linux hosts and WSL2 host with docker for windows |
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>
.
|
Happening to me too, windows 10, using WSL. |
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>
.
|
Thanks, I'll try it. Unfortunately, running it from wsl shell causes me docker/compose#7899 |
seams that did it. however the cause for this would be good to understand |
Here is what I fix this issue in docker-compose file
www.conf and zz-docker.conf is empty file
|
Hello I have the problem too.
My server runs under Ubuntu 20.04.2 LTS, only Docker and Docker-Compose and SSH are installed. I've tried several options and suggestions on the net. |
Today I checked again whether it could be done. The developers don't seem to care about the issues at the moment because it has been open for a long time. Who can recommend an alternative Docker image with phpFPM and Crontab. |
use the following https://www.github.com/webdevops/Dockerfile |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please update it if any action still required. |
This should not be closed yet. Since it still affects some |
How does it go on here? |
Yes yes... it's difficult currently. I should have more time soon. In addition, if someone would like help us to manage thoses images, s/he can contact me (we will continue to support but sometime we have less time so someone in backup maybe helpful). |
I had similar issue and found why. The message was the following :
My container was created with Portainer and the user field under Command and Logging has been set automatically to "root" instead of "nobody". The user has already been specified in the Dockerfile with So you can leave the field under portainer empty, it will be automatically assigned to nobody Or run your container with --user=nobody (i didn't try this method) |
Bro, you saved me after hours of becoming more and more suicidal. <3 |
got the exact same error, I used a script to build the dockercontainer turned out I accidentally left |
Where does this change actually get made? |
I have now discovered something strange. Docker and Portainer are running on the server, but only for administration. I currently have 8 Docker-Compose stacks running on the server. They are all structured the same: php-FPM and then redis, SQL, NGINX and an image for the SQL backup. Now my question is, if I copy the docker-compose.yml and put it in a new directory and start it. Why does the error occur when some start it and not when others start it? None of the solutions suggested here worked for me. So why does the error occur sometimes and not sometimes? |
Hi, I am starting container from
FROM thecodingmachine/php:7.4-v3-fpm
and gettingAt the local machine, everything is right but on the server, it's failing.
4.19.0-9-amd64
Any advice? One week I am trying to figure it out, what is wrong. Thank you.
The text was updated successfully, but these errors were encountered: