/vagrant 未填充文件 [英] /vagrant not populated with files

查看:14
本文介绍了/vagrant 未填充文件的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我使用 OS X (10.11.4) 上最新版本的 VirtualBox (5.0.16 r105871) 和最新的 vagrant init 的默认配置配置了 Vagrant (1.7.4)代码>ubuntu/trusty64 盒子版本 (v20160323.0.0).

I have Vagrant (1.7.4) configured with the default configuration from vagrant init using the latest version of VirtualBox (5.0.16 r105871) on OS X (10.11.4) and the latest ubuntu/trusty64 box version (v20160323.0.0).

我的 VM 具有来宾添加的匹配版本,但我似乎无法让共享的 /vagrant 目录工作./vagrant/ 目录存在于虚拟机上,但如果我在它上面运行 ls ,它是完全空的.如果我 touch 一个文件,它会出现在来宾的 /vagrant 中,但不会同步回我机器上的项目文件夹,并在重新启动时消失.VirtualBox GUI 显示共享文件夹:

My VM has the matching version of guest additions, but I can't seem to get the shared /vagrant directory to work. The /vagrant/ directory exists on the VM, but if I run ls on it it's completely empty. If I touch a file it appears on the guest in /vagrant but does not sync back to the project folder on my machine, and disappears on reboot. The VirtualBox GUI shows the shared folder:

http://i.imgur.com/yM1wuj5.png

Vagrantfile:

Vagrantfile:

# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure(2) do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://atlas.hashicorp.com/search.
  config.vm.box = "ubuntu/trusty64"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # 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"

  # 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|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
  # such as FTP and Heroku are also available. See the documentation at
  # https://docs.vagrantup.com/v2/push/atlas.html for more information.
  # config.push.define "atlas" do |push|
  #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
  # end

  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   sudo apt-get update
  #   sudo apt-get install -y apache2
  # SHELL
end

推荐答案

我已经找出问题所在 - 虽然机器上存在 /vagrant 目录,但共享文件夹没有被尽管在 GUI 中将自动挂载功能设置为开启,并且调试输出表明它确实已挂载,但 VirtualBox 会自动挂载.

I've figured out what the issue is - while the /vagrant directory existed on the machine, the shared folder was not being automatically mounted by VirtualBox, despite the auto-mount feature being set to on in the GUI, and the debug output saying that it had indeed been mounted.

手动运行 sudo mount -t vboxsf vagrant/vagrant 可以解决问题.我将此行放入我的新贵工作的预启动脚本中以启动我的服务器.

Running sudo mount -t vboxsf vagrant /vagrant manually solves the issue. I put this line into the prestart script for my upstart job to start my server.

这篇关于/vagrant 未填充文件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆