Packer Shell配置器报告运行成功,但未执行任何操作

时间:2018-06-21 23:20:15

标签: azure packer

我正在尝试使用打包程序来简单地启动VM,运行单个Shell脚本,然后存储新映像。我正在使用Azure,当我运行打包程序时,它似乎已成功完成,但是当我从新映像制作VM时,该脚本似乎无效。该脚本仅用于测试,应在主目录中创建一个文件,但登录后没有任何显示。

这是我的打包程序配置文件:

 {
   "builders": [
     {
       "type": "azure-arm",

       "client_id": "...",
       "client_secret": "...",
       "subscription_id": "...",
       "tenant_id": "...",

       "os_type": "Linux",
       "image_publisher": "Canonical",
       "image_offer": "UbuntuServer",
       "image_sku": "16.04-LTS",

       "ssh_pty" : "true",

       "capture_container_name": "container",
       "capture_name_prefix": "prefix",
       "resource_group_name": "rg",
       "storage_account": "sa",

       "location": "West US"
     }
   ],
   "provisioners": [
     {
       "type": "shell",
       "script": "test.sh"
     }
   ]
 }

这是我的脚本(test.sh):

#!/bin/bash -e
echo "This is only a test!" >> ~/test_script_output.txt

这是构建的输出:

azure-arm output will be in this color.

==> azure-arm: Running builder ...
    azure-arm: Creating Azure Resource Manager (ARM) client ...
==> azure-arm: Creating resource group ...
==> azure-arm:  -> ResourceGroupName : 'packer-Resource-Group-4zt0csjrzl'
==> azure-arm:  -> Location          : 'West US'
==> azure-arm:  -> Tags              :
==> azure-arm: Validating deployment template ...
==> azure-arm:  -> ResourceGroupName : 'packer-Resource-Group-4zt0csjrzl'
==> azure-arm:  -> DeploymentName    : 'pkrdp4zt0csjrzl'
==> azure-arm: Deploying deployment template ...
==> azure-arm:  -> ResourceGroupName : 'packer-Resource-Group-4zt0csjrzl'
==> azure-arm:  -> DeploymentName    : 'pkrdp4zt0csjrzl'
==> azure-arm: Getting the VM's IP address ...
==> azure-arm:  -> ResourceGroupName   : 'packer-Resource-Group-4zt0csjrzl'
==> azure-arm:  -> PublicIPAddressName : 'packerPublicIP'
==> azure-arm:  -> NicName             : 'packerNic'
==> azure-arm:  -> Network Connection  : 'PublicEndpoint'
==> azure-arm:  -> IP Address          : '000.000.000.000' <redacted>
==> azure-arm: Waiting for SSH to become available...
==> azure-arm: Connected to SSH!
==> azure-arm: Provisioning with shell script: test.sh
==> azure-arm: Querying the machine's properties ...
==> azure-arm:  -> ResourceGroupName : 'packer-Resource-Group-4zt0csjrzl'
==> azure-arm:  -> ComputeName       : 'pkrvm4zt0csjrzl'
==> azure-arm:  -> OS Disk           : 'https://sa.blob.core.windows.net/images/pkros4zt0csjrzl.vhd'
==> azure-arm: Powering off machine ...
==> azure-arm:  -> ResourceGroupName : 'packer-Resource-Group-4zt0csjrzl'
==> azure-arm:  -> ComputeName       : 'pkrvm4zt0csjrzl'
==> azure-arm: Capturing image ...
==> azure-arm:  -> ResourceGroupName : 'packer-Resource-Group-4zt0csjrzl'
==> azure-arm:  -> ComputeName       : 'pkrvm4zt0csjrzl'
==> azure-arm: Deleting resource group ...
==> azure-arm:  -> ResourceGroupName : 'packer-Resource-Group-4zt0csjrzl'

1 个答案:

答案 0 :(得分:0)

好,所以我有两件事要做。

第一,我不得不取消waagent的配置,以便VM能够正常启动。显然,this is required by the azure-arm type。第二点:既然用户帐户已被删除,我必须更改脚本以影响主目录之外的内容。因此,我只是在驱动器的根目录上创建了一个新文件。

这是我的新供应者部分:

"provisioners": [
  {
    "type": "shell",
    "execute_command": "chmod +x {{ .Path }}; {{ .Vars }} sudo '{{ .Path }}'",
    "script": "test.sh",
    "skip_clean": "true"
  },
  {
    "type": "shell",
    "execute_command": "chmod +x {{ .Path }}; {{ .Vars }} sudo -E sh '{{ .Path }}'",
    "inline_shebang": "/bin/sh -x",
    "inline": [
      "/usr/sbin/waagent -force -deprovision+user && export HISTSIZE=0 && sync"
    ],
    "skip_clean": "true"
  }
]

这是我的新脚本:

#!/bin/bash -e
echo "This is only a test!" >> /test_script_output.txt

侧面说明:我必须向每个预配器添加“ skip_clean”,因为它每次都无法删除脚本。我不知道为什么。