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
Stop using vagrant-triggers for Vagrant >= 2.1.0 #49
Comments
Related: should we add a constraint to the Vagrantfile our WordPress layout to restrict usage with version >= 2.1.0 of Vagrant? Currently we require at least version 1.7.4, but there is no upper limit. As a result, if a developer follows the instructions at https://seravo.com/docs/development/how-to-install/ and attempts to run vagrant with our WP layout, he/she will face the error stated above. |
Is there any way to bypass this issue? Or should I just downgrade vagrant to an older version (< 2.1.0)? |
Hi! As a temporal workaround, you could try setting the suggested |
The current work-around is to install a Vagrant version older than 2.10. You can find 2.0.4 at https://releases.hashicorp.com/vagrant/2.0.4/ |
See duplicate of this at Seravo/wordpress#88 |
This will be fixed as part of a currently on-going refactoring of the whole Vagrant bootstrap process. In the mean time added this note to docs: Seravo/docs@70bb7ec |
Vagrant 2.0.4 doesn't support Virtualbox version 6.0 and Virtualbox 6.0 is the packaged version in Ubuntu 19.04 and Fedora 30. This means that using wp-palvelu-vagrant on new distro releases even more trickery could be needed in order to make it work. |
This was fixed in Seravo/wordpress@a6bf061. Updating the Vagrantfile to the newest version should fix the trigger-related problems with Vagrant version 2.1.0 or later. |
When attempting to run
vagrant up
on Vagrant version 2.1.0 with vagrant-triggers installed, the command produces a warning and fails as a result of an exception:According to https://www.vagrantup.com/docs/triggers/, it seems that Vagrant has its own trigger mechanism which conflicts with the vagrant-triggers plugin. We should probably move away from external plugins and investigate if we could start using Vagrant's own mechanism for newer Vagrant versions, and eventually deprecate the vagrant-triggers plugin.
The text was updated successfully, but these errors were encountered: