How to fix this issue ?

MacBook-Pro-de-Max:vagrant-magento max$ bash init_project.sh [2017-10-19 18:07:33] Checking requirements [/Users/max/magento/vagrant-magento/scripts/host/check_requirements.sh] [2017-10-19 18:07:33] Installing missing vagrant plugins [init_project.sh] [2017-10-19 18:07:34] Generating random IP address, and host name to prevent collisions (if no custom values specified) [init_project.sh] [2017-10-19 18:07:34] Installing Magento dependencies via Composer [init_project.sh] [2017-10-19 18:07:34] Executing composer command [/Users/max/magento/vagrant-magento/scripts/host/composer.sh] [2017-10-19 18:07:34] > Checking requirements [/Users/max/magento/vagrant-magento/scripts/host/check_requirements.sh] [2017-10-19 18:07:34] > composer --ignore-platform-reqs --no-interaction install [/Users/max/magento/vagrant-magento/scripts/host/composer.sh] [2017-10-19 18:07:35] Initializing vagrant box [init_project.sh] [2017-10-19 18:07:36] Directory '/Users/max/magento/vagrant-magento/etc' was not mounted as expected by Vagrant. Please make sure that 'paliarush/magento2.ubuntu' Vagrant box was downloaded successfully (if not, this may help http://stackoverflow.com/questions/35519389/vagrant-cannot-find-box) And that Vagrant is able to mount VirtualBox shared folders on your environment (see https://www.vagrantup.com/docs/synced-folders/basic_usage.html ) [/Users/max/magento/vagrant-magento/scripts/host/check_mounted_directories.sh] MacBook-Pro-de-Max:vagrant-magento max$

I'm using Vagrant 2.0.0 and VirtualBox 5.2.0 on Mac OS X Sierra.

Hi guys,

I am Magento core developer and may not know all the issues you may face as a community developer. To improve current project, I am trying to collect more information about the use cases community developers have in their daily work.

I would appreciate If you could share your typical project structure and how you use this vagrant project.

Maybe there are some missing features, which could make your life easier.

Thanks Alex

When I use the bash init_proces.sh, the command line returns a error which results in a invalid Vagrant installation process.

bash: /vagrant/scripts/guest/m-clear-cache: No such file or directory This error comes up after 'Unlinking CE sample data'

Two weeks ago, it all worked perfectly on my local machine.

1. Clone repository :

git clone https://github.com/paliarush/magento2-vagrant-for-developers.git magento2-test

2. Initializing :

cd magento2-test bash init_project.sh

3. I get an error :

Message: NoMethodError: undefined method `deep_merge!' for #Hash:0x00000001504b68

I read somewhere deep_merge would be a vagrant plugin, but just a vagrant plugin install deep_merge return the same error.

Hi,

is it me, or is sample data not working currently? The default config.yaml file seems to have filled out defaults for the CE edition with sample data (only thing NOT set is the "install_sample_data" option).

Regardless of the "install_sample_data" option, the sample data isn't installed. If I attempt to deploy it manually using "bash m-bin-magento sample:deploy" (which seems it shouldn't be needed, but regardless) it fails with the following:

$ bash m-bin-magento sample:deploy
+ arguments=sample:deploy
+ cd /d/magento/vagrant-magento
+ vagrant ssh -c '$MAGENTO_ROOT/bin/magento sample:deploy'
<warning>You are running composer with xdebug enabled. This has a major impact on runtime performance. See https://getcomposer.org/xdebug</warning>
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - The requested package magento/module-sales-rule-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 2
    - The requested package magento/module-cms-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 3
    - The requested package magento/module-bundle-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 4
    - The requested package magento/module-grouped-product-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 5
    - The requested package magento/module-swatches-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 6
    - The requested package magento/module-wishlist-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 7
    - The requested package magento/module-downloadable-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 8
    - The requested package magento/module-tax-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 9
    - The requested package magento/module-catalog-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 10
    - The requested package magento/module-review-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 11
    - The requested package magento/module-offline-shipping-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 12
    - The requested package magento/module-sales-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 13
    - The requested package magento/module-widget-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 14
    - The requested package magento/module-msrp-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 15
    - The requested package magento/module-theme-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 16
    - The requested package magento/module-configurable-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 17
    - The requested package magento/module-product-links-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 18
    - The requested package magento/sample-data-media could not be found in any version, there may be a typo in the package name.
  Problem 19
    - The requested package magento/module-customer-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 20
    - The requested package magento/module-catalog-rule-sample-data could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Installation failed, reverting ./composer.json to its original content.
There is an error during sample data deployment. Composer file will be reverted.

I'm assuuming this is caused by some disparity between the used Magento2 and sample data GIT, but I'm unsure how to resolve it.

Hi,

I've noticed that the default Magento 2 CE installation is version 2.2-dev as that seems to be the default branch used by the Magento 2 CE git repo. Is there a flag / switch in config.yaml to use version 2.1 during the project initialisation process?

I'm downloading EE from a private repo. Here's what the repo section of my config.yaml looks like.

repository_url:
  # [To apply changes: init-project -fc]
  ce: "https://github.com/magento/magento2.git "
  ee: "https://github.com/LCind/magento2ee.git"

From my host machine, executing bash m-switch-to-ee returns the following:

C:\Projects\vagrant-magento>bash m-switch-to-ee
+ [[ -f /c/Projects/vagrant-magento/lib/php/php.exe ]]
+ php_executable=php
+ echo php
+ [[ ! -f /c/Projects/vagrant-magento/magento2ce/magento2ee/app/etc/aliases_to_classes_map.json ]]
+ set +x
EE codebase is not available

I'm on windows 10 and get all the way through the installation, but when I launch in browser I just see the app directory and in that only the etc directory. Any idea what I could be doing wrong?

Sorry that not post the issue, maybe to someone will be helpful. I tried to launch this Vagrant on the Windows 10 during 3 - 5 days, Faced with such issues:

1. the first was with Vagrant, the current versions of Vagrant 2.0.2 don't work properly on Windows 10. the issue https://github.com/hashicorp/vagrant/issues/9516, doesn't relate to the current Vagrant container, but it was. And maybe it was the reason why i tried the versions 1.x. After that, i decided to try another version of Vagrant, like 1.9.x and 1.8.x all these versions lead me to the issue number 2

2. The second was with mounting my.cnf, it was solved by setup "correct" version of Vagrant (2.0.1) and Vbox (5.2.6), but was issue number 3

Initializing vagrant box [init_project.sh] [2018-02-28 22:24:31] Directory '/n/magento/vm22/vagrant-magento/etc' was not mounted as expected by Vagrant. Please make sure that 'paliarush/magento2.ubuntu' Vagrant box was downloaded successfully (if not, this may help http://stackoverflow.com/questions/35519389/vagrant-cannot-find-box) And that Vagrant is able to mount VirtualBox shared folders on your environment (see https://www.vagrantup.com/docs/synced-folders/basic_usage.html ) [/n/magento/vm22/vagrant-magento/scripts/host/check_mounted_directories.sh]

3. On this step, i faced with issue below, the Vagrant container with Ubuntu didn't contain Magento codebase, was only created directory var, generated app/etc

[2018-02-28 20:35:43] Checking if all required directories were mounted successfully [/vagrant/scripts/guest/check_mounted_directories] [2018-02-28 20:35:43] > Directory '/var/www/magento2ce' was not mounted as expected and Magento code base is not accessible on the guest machine. If your host is OSX or *nix, please make sure that Vagrant is able to mount NFS shares on your environment (see https://github.com/paliarush/magento2-vagrant-for-developers/issues/88#issuecomment-254854019 ) [/vagrant/scripts/guest/check_mounted_directories]

the solution for this was updated the directive to such

        guest_magento_dir = '/var/www/magento2ce'
        config.vm.synced_folder host_magento_dir, guest_magento_dir
        config.vm.synced_folder host_magento_dir + '/var', guest_magento_dir + '/var', create: true
        config.vm.synced_folder host_magento_dir + '/generated', guest_magento_dir + '/generated', create: true
        config.vm.synced_folder host_magento_dir + '/app/etc', guest_magento_dir + '/app/etc', create: true

so i added synchronization with Magento codebase from a host machine to the guest, maybe not the best solution, but at the current moment, this works for me.

config.vm.synced_folder host_magento_dir, guest_magento_dir

at the current moment Magento works, i didn't test it well, so can't say what kind of issues can popup with Magento and Vagrant.

I just created a new project with this box and installed Magento 2.2. I'm trying to set up Grunt and I get errors like the following:

npm WARN engine [email protected]: wanted: {"node":">=4.0.0"} (current: {"node":"v0.10.25","npm":"1.3.10"})
npm WARN engine [email protected]: wanted: {"node":">=4.0.0"} (current: {"node":"v0.10.25","npm":"1.3.10"})
npm WARN engine [email protected]: wanted: {"node":">=4.0.0"} (current: {"node":"v0.10.25","npm":"1.3.10"})
npm WARN engine [email protected]: wanted: {"node":">=4.0.0"} (current: {"node":"v0.10.25","npm":"1.3.10"})
npm WARN engine [email protected]: wanted: {"node":">=4"} (current: {"node":"v0.10.25","npm":"1.3.10"})

I can't find where Node is provisioned on this box and the version from a fresh install is v0.10.25. The current stable version of Node is 8.9.1. Is Node provisioned or was it installed on the base box and that's why it's out of date?

Hi there, Been trying for days to get this working. I initially installed via git clone, and it all worked just dandy. When I choose Composer however, the installation just hangs. I've tried manually installing via the CLI after aborting the init_project script, and the installation hangs at

[Progress: 212 / 426]
Installing user configuration...

But I can't seem to get any further. I've tried disabling Xdebug completely and it still seems to be the same.

I can't figure out what's causing it to stall - especially since Git install seems to go through smoothly.

Host OS is Ubuntu 16.04.

Thanks in advance for any help.

Hello, I'm not entirely sure but I think that Deleting TestModule directories in m_reinstall.sh should only be done in case of git as checkout source In case of checkout_source_from: "composer" for example the magento2ce/app/code/Magento directory doesn't exist, because it's found in vendor directory. In this case I'm not sure it's useful to delete the TestModule directory anyway (?) Thanks

magento_app_code_dir="${vagrant_dir}/magento2ce/app/code/Magento"

mkdir -p "$magento_app_code_dir"

cd "${magento_app_code_dir}"

status "Deleting TestModule directories"
ls | grep "TestModule" | xargs rm -rf

For Windows user unzip is not installed by default in gitbash and is an implicite requirement in the project.

Please make it more explicite to Check optional unix tools during gitbash setup (like advised in this Stackoverflow answer )

Thank you so much

When I execute manually : curl http://windows.php.net/downloads/releases/archives/php-5.6.9-nts-Win32-VC11-x86.zip -o lib/php.zip it creates a small file (1kb)

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   207  100   207    0     0   1510      0 --:--:-- --:--:-- --:--:--  1522

a file that is clearly not the whole php5.6 zip (trying to unzip it manually tells me that it's not a zip file)

So I had to curl manually another version of PHP : curl https://windows.php.net/downloads/releases/php-7.4.16-nts-Win32-vc15-x64.zip -o lib/php.zip

I also had to install VC_redist.x64.exe like advised in this stackoverflow answer otherwise I get this :

php --version
PHP Warning: 'vcruntime140.dll' 14.0 is not compatible with this PHP build linked with 14.16 in Unknown on line 0

So it might be a good idea to add VC_redist.x64.exe it to the requirement and update the PHP version to download. (Or maybe to make a list of versions (list of urls) to try before renouncing the Automatic PHP host installation)

Thank you

When attempting to run the init shell script in git bash it immediately returns the following error. /c/www/vagrant-magento/scripts/output_functions.sh: line 184: /dev/fd/62: Read-only file system

I can't find any other info on the error and it doesn't look like an issue has been raised for a similar issue before.

Thanks.

Running bash init_project.sh fails. I see this message in the log:

[2019-06-10 20:05:18] STATUS: > ./bin/magento setup:install --db-host=localhost --db-name=magento --db-user=root --backend-frontname=admin --base-url=http://magento2.vagrant148/ --language=en_US --timezone=America/Chicago --currency=USD --admin-lastname=Admin --admin-firstname=Admin [email protected] --admin-user=admin --admin-password=123123q --cleanup-database --use-rewrites=1 --amqp-host=localhost --amqp-port=5672 --amqp-user=guest --amqp-virtualhost=/ --amqp-password=guest [/vagrant/scripts/guest/m-reinstall]]

Magento supports PHP 7.1.3 or later. Please read https://devdocs.magento.com/guides/v2.3/install-gde/system-requirements-tech.html

[2019-06-10 20:05:18] ERROR: > Magento installation failed. [/vagrant/scripts/guest/m-reinstall]]

When I vagrant ssh and then php --version, I see this version:

PHP 7.0.7-4+deb.sury.org~trusty+1

When I tried to update my config.yaml to php_version: "7.2" and vagrant reload I see two messages regarding PHP:

update-alternatives: error: alternative /usr/bin/php7.2 for php not registered; not setting ERROR: Module php7.1 does not exist! [Unknown source file] ERROR: Module php7.2 does not exist! [Unknown source file]

And when I ssh into the box and look at the contents of /usr/bin/: