为什么我无法在packer构建过程中运行"source"命令？

Question

我正在尝试进行packer构建。

我的源AMI是一个Ubuntu系统。我想安装并运行Python虚拟环境。

我的provisioner如下所示。apt-get正常工作并创建了virtualenv。但是，当我在activate上执行source时，它失败了。我收到以下错误：/tmp/script.sh: 53: /tmp/script.sh

似乎我不能在我的packer构建中运行source。我该如何解决这个问题？我需要在其中运行virtualenv并执行pip install。

  "provisioners": [

    {
      "type": "shell",
      "inline": [
        "echo '70'",
        "sudo apt-get --assume-yes install python-virtualenv",
        "echo '80'",
        "sudo virtualenv /home/myuser/myVirtualEnv",
        "echo '90'",
        "ls -altr /home/myuser/myVirtualEnv/bin",
        "echo '95'",
        "source /home/myuser/myVirtualEnv/bin/activate",
        "echo '100'",
      ]
    }
  ]

这是控制台输出：

  myHostName: 70
  myHostName: Reading package lists... Done
  myHostName: Building dependency tree
  myHostName: Reading state information... Done
  myHostName: The following NEW packages will be installed:
  myHostName: python-virtualenv
  myHostName: 0 upgraded, 1 newly installed, 0 to remove and 125 not upgraded.
  myHostName: Need to get 1,485 kB of archives.
  myHostName: After this operation, 1,935 kB of additional disk space will be used.
  myHostName: Get:1 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ trusty/universe python-virtualenv all 1.11.4-1 [1,485 kB]
  myHostName: Fetched 1,485 kB in 0s (22.5 MB/s)
  myHostName: Selecting previously unselected package python-virtualenv.
  myHostName: (Reading database ... 56592 files and directories currently installed.)
  myHostName: Preparing to unpack .../python-virtualenv_1.11.4-1_all.deb ...
  myHostName: Unpacking python-virtualenv (1.11.4-1) ...
  myHostName: Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
  myHostName: Setting up python-virtualenv (1.11.4-1) ...
  myHostName: 80
  myHostName: New python executable in /home/myuser/myVirtualEnv/bin/python
  myHostName: Installing setuptools, pip...done.
  myHostName: 90
  myHostName: total 3312
  myHostName: lrwxrwxrwx 1 root root       6 Jun 25 17:21 python2.7 -> python
  myHostName: lrwxrwxrwx 1 root root       6 Jun 25 17:21 python2 -> python
  myHostName: -rwxr-xr-x 1 root root 3345416 Jun 25 17:21 python
  myHostName: -rwxr-xr-x 1 root root     254 Jun 25 17:21 easy_install-2.7
  myHostName: -rwxr-xr-x 1 root root     254 Jun 25 17:21 easy_install
  myHostName: -rwxr-xr-x 1 root root     226 Jun 25 17:21 pip2.7
  myHostName: -rwxr-xr-x 1 root root     226 Jun 25 17:21 pip2
  myHostName: -rwxr-xr-x 1 root root     226 Jun 25 17:21 pip
  myHostName: drwxr-xr-x 6 root root    4096 Jun 25 17:21 ..
  myHostName: -rw-r--r-- 1 root root    1129 Jun 25 17:21 activate_this.py
  myHostName: -rw-r--r-- 1 root root    2476 Jun 25 17:21 activate.fish
  myHostName: -rw-r--r-- 1 root root    1263 Jun 25 17:21 activate.csh
  myHostName: -rw-r--r-- 1 root root    2207 Jun 25 17:21 activate
  myHostName: drwxr-xr-x 2 root root    4096 Jun 25 17:21 .
  myHostName: 95
  myHostName: /tmp/script.sh: 53: /tmp/script.sh: source: not found
  myHostName: 100

- Saqib Ali

Answer 1

请注意故障排除部分中关于shell脚本的注释，此处。默认情况下，Packer使用Ubuntu上的dash shell（/bin/sh）。dash shell不支持“source”命令。您可以尝试以下方法：

• 使用“.”代替source
• 在Packer文件中指定inline_shebang
• 使用“script”而非“inline”

- mark

---

非常有帮助 :). 他们说：“如果你的脚本中有bash特定的命令，那么请在脚本顶部加上 #!/bin/bash -e。” - another

Answer 2

您只能在shell内进行源操作，而您没有该权限。不过，有一个更简单的解决方案，那就是直接使用虚拟环境中提供的二进制文件。

$ virtualenv foobarbaz
$ foobarbaz/bin/python -c 'import sys; print sys.prefix;'

这说明了概念，使用pip也可以以同样的方式工作。

- deets

---

谢谢。我应该运行什么命令来使用pip而不是你展示的原始Python代码使其工作？ - Saqib Ali

Pip？它在同一位置。并且显示在您自己的输出中。 - deets

Answer 3

打包构建HCL文件：

build {
  provisioner "shell" {
    script = "../scripts/setup.sh"
  }
}

在 setup.sh 中，将 source 替换为 .：

#!/bin/bash

. env/bin/activate

- Sarah Dwyer