I'm building an AMI with Hashicorp Packer and this are one of the steps:
{
"type": "shell",
"script": "scripts/apt.sh"
},
{
"type": "shell",
"inline": ["sudo reboot"],
"inline_shebang": "/bin/bash -e",
"expect_disconnect": true
},
{
"type": "shell",
"script": "scripts/sysctl.sh",
"pause_before": "10s"
},
and here the result:
Provisioning with shell script: scripts/apt.sh
==> amazon-ebs: Provisioning with shell script: /tmp/packer-
shell376239929
==> amazon-ebs: Pausing 10s before the next provisioner...
==> amazon-ebs: Provisioning with shell script: scripts/sysctl.sh
amazon-ebs: net.ipv4.ip_forward = 0
amazon-ebs: net.ipv4.conf.all.send_redirects = 0
amazon-ebs: net.ipv4.conf.default.send_redirects = 0
It is pretty visible that Packer doesn't somehow interpret the reboot
command but immediately run the next command even though I put there the
pause attribute. It waits for that 10sec but then no reboot happens.
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/packer-tool/192be612-e326-4e2f-a23f-bdff450c05d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
