-
Notifications
You must be signed in to change notification settings - Fork 475
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
Fix php8.0-dev depending on php8.1-cli #316
Conversation
This fixed the issue for me. Also, this is affecting previous Sail versions. I don't know how the maintenance policy is for this project, but I was using Sail If previous versions are to be maintained this fix should be cherry picked to those. |
@mist-01 Do we have a list of the other recommended packages that would not be installed? I'm a little worried this is just going to break other things. |
I'm not OP but this is the list:
|
For me problem was solved when I added to Dockerfile this code after |
This could work too, it will leave php8.1 installed on the container. Options mentioned so far:
Any thoughts on which one is least likely to break something else? |
Personally I think "Add update-alternatives --set php /usr/bin/php8.0 call" is safest. |
Fixes #314
As described in #314, the php8.0 runtime installs packages which recommend php-pear which depends on the most recent version of php (8.1). The results in php8.1 getting installed as the default runtime. The PR suggest adding –no-install-recommends to the apt-get command in the Dockerfile to prevent the recommendations from being installed.
I tried this change out and it did prevent php8.1 from being installed. However, it does mean that php-pear (and any other recommends) are not installed. As far as I am aware, sail does not depend on php-pear and the container seems to run fine without it (default Laravel page opens in the browser).
We could also fix this by running an apt-get remove php8.1-cli in the dockerfile after line 31 if we would rather leave recommended packages installed. Thoughts?