-
Notifications
You must be signed in to change notification settings - Fork 53
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
FPM initialization failed #64
Comments
Hrmm, I have not been able to reproduce that. I am testing with the following compose file: docker-compose.yml
Logs from initial startup:
Permissions
Can I get your compose file to test and attempt to reproduce locally? Can you also tell me the version of docker and compose you are running so I can try to replicate things from that front as well. |
Thanks for checking into this. Here's the info: Version Info
docker-compose.yml
Logs
|
Updated a few things that I hope solved the issue in your environment. I still could not get it to happen for me. Can you please test the following compose (simply using
The end result should make the permissions as follows
|
All working. Web service started up with no errors. Odd that you didn't see the same thing while testing. I'm not sure why our environment's would be any different, but thanks for the help with this. Glad it's working now.
Thanks, |
Awesome, thanks for testing and validating things (^_^)/ |
Closing, this has now been pushed to |
Hi Sean, I was just going to try out the recent changes and seeing the following error after starting a test container with new volumes. I believe the www.sock file needs a permission change to either be owned by apache although I'm not completely sure.
Let me know if there's any further info you need.
Thanks,
Kevin
The text was updated successfully, but these errors were encountered: