-
-
Notifications
You must be signed in to change notification settings - Fork 642
6.0.0 and PHP 7.3.x #2076
Comments
Did find a workaround—in config.yml, changed the value in What's odd is that this only affects PHP 7.3 builds, not 7.4. The error message indicated that the socket is already in use, even though I was careful to run |
Can you run |
Can you also check if you've overridden the |
The default is set here: https://github.com/geerlingguy/ansible-role-php-mysql/blob/master/vars/Debian.yml#L2 And it looks like maybe you're installing two versions of the library (which installs two versions of PHP on the system). Also make sure you do a full |
Thanks—
I went ahead and reset to defaults in the config.yml file, and ran The build process got to this point and failed:
I then, as a check, ran this again:
So, I reset the Per the Ansible settings, where would this be modified? I have made no changes to DrupalVM code besides the config.yml, and cross-checked this against the new default.config.yml. To check, I ran this again with 7.3 up, and the response looks the same as before:
|
Hi All :)
The version 2.0.10 has a problem with provisioned PHP 7.3. Regards. |
geerlingguy/ansible-role-php-versions#51 should fix it. |
If someone wants to patch it manually (or with composer-patches package) until there's a new release, here's a patch https://github.com/oxyc/drupal-vm/commit/cec3dd6487a7ab5f2b1d315044e512b3695070d1.patch |
I did a workaround on my vagrant box to update the php version from 7.4 to 7.3. I manually changed the mapping like this:
This fixed the php version for me to 7.3 |
@pranitjha Good that you found a solution. If you have to rebuild your VM though, will you have to repeat this process? |
@charlieartist I did |
@pranitjha Good. My real issues have come with major updates, when |
Sorry about all this; I'm going to merge @oxyc's fix and that will be in the 6.0.1 version of Drupal VM. Leaving this open until I get the role tested, tagged, and merged. |
I updated to 6.0.0, but have run into some lingering issues regarding running PHP 7.3, where Ansible errors are popping up at the end of the build process. The CLI output is as follows:
I can get the build stood up by running
vagrant reload --provision
, but it stands up running PHP 7.4.9. This is true as well when I runvagrant halt
followed byvagrant up
, even though the config.yml file lists this:To be sure I hadn't overlooked anything, I did the following:
vagrant destroy
followed byvagrant up
Ironically, the main reason I was updating Drupal VM to the latest was because of the PHP 7.4/7.3 issue I was experiencing in the older version.
The text was updated successfully, but these errors were encountered: