shopt manual :
If set, Bash includes filenames beginning with a ‘.’ in the results of filename expansion.
Run this command first
shopt -s dotglob
Run your command
mv * /newlocation
Open the ovf file in notepad
Remove the CD-ROM item lines from the ovf file. For some reason, the CD-ROM directives are the ones causing the issue.
You can always add a new CD-ROM after the machine is created.
I do not quite have time to find out the real problem but when i do, i will go back and edit this post.
<Item ovf:required="false"> <rasd:AddressOnParent>0</rasd:AddressOnParent> <rasd:AutomaticAllocation>false</rasd:AutomaticAllocation> <rasd:ElementName>CD-ROM 1</rasd:ElementName> <rasd:InstanceID>9</rasd:InstanceID> <rasd:Parent>4</rasd:Parent> <rasd:ResourceSubType>vmware.cdrom.iso</rasd:ResourceSubType> <rasd:ResourceType>15</rasd:ResourceType> <vmw:Config ovf:required="false" vmw:key="connectable.allowGuestControl" vmw:value="true" /> </Item>
Also remove the .mf file. This file is used for integrity check.
Now you should be able to deploy your OVF file.
Make sure that you have composer installed and upgrade it if you have to.
Something like that will do it on a Ubuntu platform
sudo apt-get install composer
run the following command:
composer global require drupal/console:@stable
Create your Drupal Folder
mkdir new_foler cd new_folder
composer create-project \ drupal-composer/drupal-project:8.x-dev new_foler \ --prefer-dist \ --no-progress \ --no-interaction
If you are getting this error
[ERROR] Command "site:install", is not a valid command name.
after installing drupal console, it it because you are running the command outside a drupal installation folder. The confusion is the fact that most of us expect a “site:install” to go out and retrieve the drupal files for us but the command is not doing that.
The site:install allows us to install drupal from the command line. It DOES NOT retrieve Drupal files for you.
It took me a while to figure this out.