-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Composer in combination with PHP-FPM container #1362
Comments
Same error..... please help me |
I'm having the same problem |
Any luck with this? I have the same issue with LDAP |
@wvdongen workspace and php-fpm is different container. you must install SOAP both:
then run |
@bestlong I know it is a different container (I've mentioned this in my first post). It makes no sense to install all php extensions also in your workspace container. Then you might as well use |
Hello everyone, I had same issue. I am running php via xampp and recently I tried installing a Laravel project (Windows). When running |
@wvdongen I misunderstood. i remade it again, It looks like no problem
|
@arvinakori @abhaymaurya your comments have nothing to do with the issue that has been described! The problem is that Composer is run from the workspace container , but PHP for the app with all the extensions are running in the PHP-FPM container. So in order to use composer you would have to install all PHP extensions in both containers. It makes no sense to install all php extensions also in your workspace container. Then you might as well use --ignore-platform-reqs using composer. |
I tried several ways, but the only one that resolved provisionally was this: https://stackoverflow.com/questions/48056498/e-package-php-soap-has-no-installation-candidate-on-php7-0-fpm-docker-imag |
Strangely when I follow @bestlong's steps, the exact same error is gone on my installation. Is this issue already fixed? I did this: edited .env file:
Then I ran: The output of
|
That's not strange at all, because composer runs in the workspace container and you've installed SOAP there. The whole issue in this ticket is that your application uses the PHP-FPM container, so ideally composer should check those extensions and not in the workspace. So as previously said in #1362 (comment) It makes no sense to install all php extensions also in your workspace container. Then you might as well use --ignore-platform-reqs using composer. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi again 👋 we would like to inform you that this issue has been automatically |
I meet this same issue too,and follow this steps solved my problem,thanks. |
Detener los contenedores |
@ednoreyes Waarom praat je Spaans als iedereen Engels praat? Dit begrijp je toch ook niet? In short please continue the discussion in English. |
Tried all the above and composer still didn't see the ext-gmp, because it was not installed properly in workspace. I had to add
right before the
in the workspace Dockerfile, even if the apt-get is executed in the beginning of the Dockerfile. |
it's works for me. |
My PHP-FPM 7 container has been configured with:
PHP_FPM_INSTALL_SOAP=true
In the
phpinfo()
output I verified that SOAP was installed.When I run
composer install
in my workspace I get the following error:composer.json contains:
I've done a
composer self-update
, this doesn't fix the problem.Output of
composer show -p
doesn't list soapI’m no docker expert, but it seems Composer works with the PHP-CLI version (http://laradock.io/documentation/#change-the-php-cli-version) in the workspace and does nothing with the PHP-FPM container.
Doesn’t it make sense to add a composer install option for the PHP-FPM container? It makes no sense to install all php extensions also in your workspace container. Then you might as well use --ignore-platform-reqs using composer.
The text was updated successfully, but these errors were encountered: