scp将无法在vagrant box中的bash脚本中运行

时间:2014-08-13 20:06:49

标签: linux bash vagrant

我正在使用vagrant 1.6.3版本和一个默认的linux box for vagrant。

我的框运行正常,所以在vagrantfile中我添加了运行外部shell脚本。该脚本包含此命令。

custom.sh文件

#!/bin/bash

DEPLOY_PASSWORD="xxxxx" &&
DB_NAME="test-sync.sql.gz" &&
apt-get install sshpass &&
sshpass -p "$DEPLOY_PASSWORD" scp -P 22 -v user@test01.admin.com:"~/mysql_dumps/$DB_NAME" "./"

我尝试手动运行该命令,它运行正常,没有任何问题,但它无法使用bash脚本。这是我通过运行vagrant配置获得的错误日志:

 The following SSH command responded with a non-zero exit status.
 Vagrant assumes that this means the command failed!
 chmod +x /tmp/vagrant-shell && /tmp/vagrant-shell test-sync.sql.gz

Vagrantfile

    Vagrant.configure("2") do |config|

  # Load config JSON.
  config_json = JSON.parse(File.read("config.json"))

  # Prepare base box.
  config.vm.box = "precise32"
  config.vm.box_url = "http://files.vagrantup.com/precise32.box"

  # Configure networking.
  config.vm.network :private_network, ip: config_json["vm"]["ip"]

  # Configure forwarded ports.
  config.vm.network "forwarded_port", guest: 35729, host: 35729, protocol: "tcp", auto_correct: true
  config.vm.network "forwarded_port", guest: 8983, host: 8983, protocol: "tcp", auto_correct: true
  # User defined forwarded ports.
  config_json["vm"]["forwarded_ports"].each do |port|
    config.vm.network "forwarded_port", guest: port["guest_port"],
      host: port["host_port"], protocol: port["protocol"], auto_correct: true
  end

  # Customize provider.
  config.vm.provider :virtualbox do |vb|
    # RAM.
    vb.customize ["modifyvm", :id, "--memory", config_json["vm"]["memory"]]

    # Synced Folders.
    config_json["vm"]["synced_folders"].each do |folder|
      case folder["type"]
      when "nfs"
        config.vm.synced_folder folder["host_path"], folder["guest_path"], type: "nfs"
        # This uses uid and gid of the user that started vagrant.
        config.nfs.map_uid = Process.uid
        config.nfs.map_gid = Process.gid
      else
        config.vm.synced_folder folder["host_path"], folder["guest_path"]
      end
    end
  end

  # Run initial shell script.
  config.vm.provision :shell, :path => "chef/shell/initial.sh"

  # Customize provisioner.
  config.vm.provision :chef_solo do |chef|
    chef.json = config_json
    chef.custom_config_path = "chef/solo.rb"
    chef.cookbooks_path = ["chef/cookbooks/berks", "chef/cookbooks/core", "chef/cookbooks/custom"]
    chef.data_bags_path = "chef/data_bags"
    chef.roles_path = "chef/roles"
    chef.add_role "vdd"
  end

  # Run final shell script.
  config.vm.provision :shell, :path => "chef/shell/final.sh", :args => config_json["vm"]["ip"]
  #custom tasks
  config.vm.provision :shell, :path => "custom.sh", :args => config_json["test_config"]["db_name"]
end

2 个答案:

答案 0 :(得分:1)

我没有使用sshpass(在脚本中明确使用密码的想法让我感到畏缩),但是man-page似乎建议在脚本中你应该设置变量SSHPASS而不是使用-p咒语...

EXAMPLES
   Run rsync over SSH using password authentication, passing the password on the command line:
   rsync --rsh='sshpass -p 12345 ssh -l test' host.example.com:path .
   To do the same from a bourne shell script in a marginally less exposed way:
   SSHPASS=12345 rsync --rsh='sshpass -e ssh -l test' host.example.com:path .

答案 1 :(得分:0)

仅当提示以sshpass结尾时,

assword:才有效。在您的情况下,它将是password for user@test01.admin.com,因为您指定了用户名。

请参阅http://sourceforge.net/p/sshpass/code/HEAD/tree/trunk/main.c第362行

为什么不使用public key autentication