Failed to install the latest magento: service "phpfpm" is not running container #1

[serhii-smirnov-cps]

Description Failed to install the latest magento on Os X 13.3 (22E252)

Username and password fields were provided from adobe access keys

Steps To Reproduce

magento-docker macbook$ curl -s https://raw.githubusercontent.com/markshust/docker-magento/master/lib/onelinesetup | bash -s -- magento.test 2.4.6 community
mv: rename compose/bin to ./bin: Directory not empty
mv: rename compose/env to ./env: Directory not empty
mv: rename compose/template to ./template: Directory not empty
mv: rename compose/.vscode to ./.vscode: Directory not empty
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint: 
hint: 	git config --global init.defaultBranch <name>
hint: 
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint: 
hint: 	git branch -m <name>
Initialized empty Git repository in /Users/macbook/Projects/CoinPayments/magento-docker/.git/
There must be at least 6GB of RAM allocated to Docker to continue.

Composer authentication required (repo.magento.com public and private keys):
    Username:
    Password:

service "phpfpm" is not running container #1
fork/exec /Applications/Docker.app/Contents/Resources/bin/com.docker.cli: bad file descriptor
Composer auth has been set up.
Fixing filesystem ownerships...
service "phpfpm" is not running container #1
Filesystem ownerships fixed.
service "phpfpm" is not running container #1
service "phpfpm" is not running container #1

Expected Result

Actual Result

[AlecBlance]

Just happened to me but in windows using wsl. I fixed it by allocating 6gb ram to my wsl then reinstalling docker magento. I don't know with OS X though.

[albertopriore]

@AlecBlance worked for me with OS X

[AngeloZou]

I ran into the same problem. The website worked fine two days ago, but it cannot be opened today. https://github.com/markshust/docker-magento/issues/804#issuecomment-1586554633

[ssx]

This is caused by an outdated nginx.conf.sample file in your project.

It can't find the upstream FastCGI backend because the name is 'phpfpm' and not 'php-fpm' as it is set is some older nginx.conf.sample files.

Update your nginx.conf.sample file to the latest version and it'll likely work again: https://raw.githubusercontent.com/magento/magento2/2.4-develop/nginx.conf.sample

[AngeloZou]

This is caused by an outdated nginx.conf.sample file in your project.

It can't find the upstream FastCGI backend because the name is 'phpfpm' and not 'php-fpm' as it is set is some older nginx.conf.sample files.

Update your nginx.conf.sample file to the latest version and it'll likely work again: https://raw.githubusercontent.com/magento/magento2/2.4-develop/nginx.conf.sample

ssx, Thank you for helping me. Now my website works fine. I'm wondering why my container stops automatically, I didn't configure anything.

[ssx]

@AngeloZou that's a good question - I'd do a bin/removall, then bin/update and re-setup your containers. Definitely seems like something went a bit odd along the way. 🙂

[AngeloZou]

@AngeloZou that's a good question - I'd do a bin/removall, then bin/update and re-setup your containers. Definitely seems like something went a bit odd along the way. 🙂

Yes, I failed to install the first time, then deleted the container and reinstalled containers. I follow the method below. https://github.com/markshust/docker-magento#install-fails-because-project-directory-is-not-empty