The development team is already using vagrant on a large scale. Today want to directly on the mobile hard disk to build a back-end service call box for other students to use, directly to the Vagrant_home point to the mobile hard disk.
Export VAGRANT_HOME=/MEDIA/FLOATING/DATA_DISK/.VAGRANT.D
然后就一路标准操作:
Vagrant box Add backend_services_base ~/ubuntu-14.04-amd64-vbox.boxmkdir backend_services_basecd Backend_services_ Basevagrant Init backend_services_basevagrant up
Here's the problem:
Vagrant is stuck here until it expires.
At first it was assumed that the virtualization settings in the BIOS were not turned on, causing the VirtualBox to not be virtualized properly, and that the virtualization settings were not disabled after the check. More magical is in the Vagrantfile GUI switch open and run, found that VirtualBox normal startup, and sshd service is normal.
Is confused when, suddenly remembered to move the hard disk is to root user to load, whether is this cause? Turn vagrant Document, sure enough there is a problem.
Because the vagrant uses the private key to access the virtual machine via SSH, the SSH protocol requires that the private key file owner must be the current user. REDIRECT private key path to the current user's home, one pass at a time. :)
Config.ssh.private_key_path= "/home/floating/.vagrant.d/insecure_private_key"
Problems with using vagrant to set up box on mounted mobile hard drive