我是流浪工具的新手。
我正在使用Ubuntu 13.04
我的项目目录是" / var / www / project"。
我已通过以下命令设置了Vagrantfile。
vagrant init test_box http://cloud-images.ubuntu.com/vagrant/saucy/current/saucy-server-cloudimg-amd64-vagrant-disk1.box
Vagrantfile已成功创建。
以下是文件的内容
# -*- mode: ruby -*-
# vi: set ft=ruby :
# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
# All Vagrant configuration is done here. The most common configuration
# options are documented and commented below. For a complete reference,
# please see the online documentation at vagrantup.com.
# Every Vagrant virtual environment requires a box to build off of.
config.vm.box = "test_box"
# The url from where the 'config.vm.box' box will be fetched if it
# doesn't already exist on the user's system.
config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/saucy/current/saucy-server-cloudimg-amd64-vagrant-disk1.box"
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
# config.vm.network "forwarded_port", guest: 80, host: 8080
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network "private_network", ip: "192.168.33.10"
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network "public_network"
# If true, then any SSH connections made will enable agent forwarding.
# Default value: false
# config.ssh.forward_agent = true
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
config.vm.provider "virtualbox" do |vb|
# # Don't boot with headless mode
vb.gui = true
#
# # Use VBoxManage to customize the VM. For example to change memory:
vb.customize ["modifyvm", :id, "--memory", "1024"]
end
#
# View the documentation for the provider you're using for more
# information on available options.
# Enable provisioning with Puppet stand alone. Puppet manifests
# are contained in a directory path relative to this Vagrantfile.
# You will need to create the manifests directory and a manifest in
# the file test_box.pp in the manifests_path directory.
#
# An example Puppet manifest to provision the message of the day:
#
# # group { "puppet":
# # ensure => "present",
# # }
# #
# # File { owner => 0, group => 0, mode => 0644 }
# #
# # file { '/etc/motd':
# # content => "Welcome to your Vagrant-built virtual machine!
# # Managed by Puppet.\n"
# # }
#
# config.vm.provision "puppet" do |puppet|
# puppet.manifests_path = "manifests"
# puppet.manifest_file = "site.pp"
# end
# Enable provisioning with chef solo, specifying a cookbooks path, roles
# path, and data_bags path (all relative to this Vagrantfile), and adding
# some recipes and/or roles.
#
# config.vm.provision "chef_solo" do |chef|
# chef.cookbooks_path = "../my-recipes/cookbooks"
# chef.roles_path = "../my-recipes/roles"
# chef.data_bags_path = "../my-recipes/data_bags"
# chef.add_recipe "mysql"
# chef.add_role "web"
#
# # You may also specify custom JSON attributes:
# chef.json = { :mysql_password => "foo" }
# end
# Enable provisioning with chef server, specifying the chef server URL,
# and the path to the validation key (relative to this Vagrantfile).
#
# The Opscode Platform uses HTTPS. Substitute your organization for
# ORGNAME in the URL and validation key.
#
# If you have your own Chef Server, use the appropriate URL, which may be
# HTTP instead of HTTPS depending on your configuration. Also change the
# validation key to validation.pem.
#
# config.vm.provision "chef_client" do |chef|
# chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
# chef.validation_key_path = "ORGNAME-validator.pem"
# end
#
# If you're using the Opscode platform, your validator client is
# ORGNAME-validator, replacing ORGNAME with your organization name.
#
# If you have your own Chef Server, the default validation client name is
# chef-validator, unless you changed the configuration.
#
# chef.validation_client_name = "ORGNAME-validator"
end
当我运行命令vagrant up
时,它会打开带有空白屏幕的虚拟框,并且我在终端上获得的命令日志如下所示。
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Error: Connection timeout. Retrying...
default: Error: Connection timeout. Retrying...
default: Error: Connection timeout. Retrying...
default: Error: Connection timeout. Retrying...
default: Error: Connection timeout. Retrying...
default: Error: Connection timeout. Retrying...
default: Error: Connection timeout. Retrying...
default: Error: Connection timeout. Retrying...
default: Error: Connection timeout. Retrying...
default: Error: Connection timeout. Retrying...
default: Error: Connection timeout. Retrying...
流浪者的版本是:Vagrant 1.5.1
虚拟盒的版本是:4.3.10r93012
请在这个过程中指导我关于事情出错的地方?
如果需要任何预配置,请告诉我。
提前致谢。
答案 0 :(得分:3)
你好@Ghanshyam Dobariya,
以下步骤为我工作
第1步 将以下virtualbox apt添加到 /etc/apt/sources.list
deb http://download.virtualbox.org/virtualbox/debian precise contrib
第2步下载并注册密钥
wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc -O- | sudo apt-key add -
sudo apt-get update
第3步从https://www.virtualbox.org/wiki/Linux_Downloads下载相应的VirtualBox设置(我为Debian 7 wheezy x64做了)并使用以下命令进行安装。
dpkg -i virtualbox-4.3_4.3.10-93012~Debian~wheezy_amd64.deb
#Fix dependence issues (if exists)
apt-get -f install
第4步安装必需的软件包
sudo apt-get install dkms
sudo apt-get install dpkg-dev virtualbox-dkms
#install linux headers for your distro
sudo apt-get install linux-headers-$(uname -r)
#reconfigure virtualbox-dkms
sudo dpkg-reconfigure virtualbox-dkms
第5步从以下网址下载exact32.box图片
http://hashicorp-files.vagrantup.com/precise32.box
第6步添加流浪汉
$vagrant box add precise32 ~/Downloads/precise32.box
成功后你应该得到类似的输出
==> box: Adding box 'precise32' (v0) for provider:
box: Downloading: file:///home/ravi/Downloads/precise32.box
==> box: Successfully added box 'precise32' (v0) for 'virtualbox'!
第7步为项目创建根目录并导航到
mkdir test_project
cd test_project
接下来,运行初始化命令:
vagrant init
这将在此文件夹中创建一个Vagrantfile,它将成为项目配置的中心文件。但在我们使用刚刚添加的框部署客户机之前,请编辑Vagrantfile:
找到以下行:
config.vm.box = "base"
并将其替换为:
config.vm.box = "precise32"
这将告诉它使用这个新盒子。保存文件并退出。现在,您可以使用以下命令部署来宾计算机:
vagrant up
这将显示运行Ubuntu 12.04 LTS的VPS。要使用它,您可以轻松地SSH到它:
$vagrant ssh
Welcome to Ubuntu 12.04 LTS (GNU/Linux 3.2.0-23-generic-pae i686)
* Documentation: https://help.ubuntu.com/
Welcome to your Vagrant-built virtual machine.
Last login: Fri Sep 14 06:22:31 2012 from 10.0.2.2
vagrant@precise32:~$ _
了解更多信息,read
答案 1 :(得分:2)
如果运行64位vm,您可能需要查看本地计算机BIOS设置以启用任何VM功能。我在本地运行Windows 7,在联想笔记本电脑上运行ubuntu / trusty64。我必须在BIOS中启用虚拟化设置,然后连接超时就消失了。
答案 2 :(得分:1)
图片[Ubuntu精确32 VirtualBox] - http://files.vagrantup.com/precise32.box
工作正常,
Official Ubuntu 13.04 daily Cloud Image i386 (No Guest Additions)和Official Ubuntu 13.04 daily Cloud Image amd64 (No Guest Additions)可能存在一些问题,因为那些盒子仍然无法在我的电脑上使用。
答案 3 :(得分:1)
尝试打开防火墙上的端口22。
使用Oracle VM VirtualBox Manager直接启动VM 或
将此添加到您的Vagrantfile
config.vm.provider :virtualbox do |vb|
vb.gui = true
end
并运行“vagrant up”
使用默认漫游凭据登录
user: vagrant
pass: vagrant
添加防火墙规则
sudo ufw allow 22
答案 4 :(得分:1)
我遇到了连接超时的相同问题,并且通过从我的系统BIOS启用虚拟化解决了这个问题。 希望它可以帮助某人解决同样的问题。