【问题标题】:Vagrant bash script not respondingVagrant bash脚本没有响应
【发布时间】:2019-03-19 20:00:27
【问题描述】:

我正在学习 vagrant 并尝试编辑我的项目的 vagrantfile 以安装一些必要的包、更新等。

下面的代码是我的 bootstrap.sh bash 脚本。这有点粗糙,但它应该有效但没有。

#!/usr/bin/env bash

echo "Updating ...."
apt-get update -y > /dev/null

echo "Upgrading ..."
apt-get upgrade -y > /dev/null

echo "Installing packages ..."
apt-get install taskel tree -y > /dev/null

echo "Installing drush ..."
wget https://github.com/drush-ops/drush/releases/download/8.1.17/drush.phar > /dev/null
mv drush.phar drush > /dev/null
mv drush /usr/local/bin/drush > /dev/null
chmod +x /usr/local/bin/drush > /dev/null
drush version > /dev/null

if ! [ -L /var/www ]; then
  # rm -rf /var/www
  # ln -fs /vagrant /var/www
fi

我的 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://vagrantcloud.com/search.
  config.vm.box = "hashicorp/precise64"

  # 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.
  # NOTE: This will enable public access to the opened port
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine and only allow access
  # via 127.0.0.1 to disable public access
  # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"

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

  # 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
  #   apt-get update
  #   apt-get install -y apache2
  # SHELL

  Vagrant.configure("2") do |config|
    config.vm.box = "hashicorp/precise64"
    config.vm.provision :shell, path: "preplogs/bootstrap.sh"
  end

end

我运行 vagrant up 但没有指示 bootstrap.sh 执行,当我 ssh 进入盒子时,我的包都没有安装。

【问题讨论】:

  • vagrant reload 有帮助吗?您的规定没有被阅读,它只在 1 日阅读vagrant up
  • @brokenfoot 没有!我执行了 vagrant reload, vagrant up 然后 vagrant ssh 但我的脚本仍然没有生效。
  • vagrant reload &amp;&amp; vagrant ssh 应该足够了。你可以strace vagrant reload &amp;&amp; vagrant ssh 看看它是否在尝试读取配置脚本、什么路径等。
  • 我刚试过这个,效果很好!我将Vagrantfilebootstrap.sh 放在同一个目录中,然后将vagrant up 放在同一个目录中,并且更新按预期运行。如果您 vagrant destroy -f 实例并再次尝试 up 会发生什么?
  • 还是不明白这个。我对上述建议的尝试都没有奏效

标签: bash vagrant


【解决方案1】:

我终于明白了。

我复制了 Vagrant.configure("2") do |config|end 部分。 如果您查看我的问题中的完整 Vagrantfile 内容,您会发现我做错了什么。

直到我在编辑器而不是终端中打开文件之前,我并不清楚。

感谢@brokenfoot 和@Jon 的帮助和意见。

【讨论】:

    猜你喜欢
    • 1970-01-01
    • 2016-04-04
    • 2010-12-08
    • 1970-01-01
    • 2017-12-03
    • 1970-01-01
    • 2015-02-16
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多