-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Process] Error: proc_open(): posix_spawn() failed: No such file or directory in /app/vendor/symfony/process/Process.php:371
#57722
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
Comments
Can you create a small example application that allows to reproduce your issue? |
Do you have the |
@xabbuh I will try to recreate a sample application later today. @nicolas-grekas No, the PHP-FPM image does not contain $ docker run --rm -it --entrypoint=/bin/sh t0shy/phpfpm-bookworm:8.3.9 git -v
/bin/sh: 0: cannot open git: No such file This was never an issue until I bumped What would be the recommended approach/workaround for this, without the need of installing |
This then rather looks like something to handle in GrumPHP (maybe that's already configurable?). If git is not installed, looking for its working directory does not make much sense to me. |
We need to acknowledge that the behavior changed with #52409: when a command is not available, we now know it right away and we throw a ProcessStartFailedException. Before the command always started successfully because of the |
@xabbuh In case it's still needed, I've created an example repo: https://github.com/ToshY/symfony-57722 |
Closing as duplicate of #57946, let's continue there. |
Uh oh!
There was an error while loading. Please reload this page.
Symfony version(s) affected
7.1
Description
Upgrading
symfony/process
from7.0.8
to7.1.1
breaks commiting withphpro/grumphp:^2.0
.How to reproduce
phpro/grumphp:^2.0
(dev) andsymfony/process:7.1.*
8.3.8
.Example grumphp config
grumphp.yml
Possible Solution
Using
7.0.8
until fixed.Additional Context
Possibly related to #52409
Reproduction example
https://github.com/ToshY/symfony-57722
The text was updated successfully, but these errors were encountered: