summaryrefslogtreecommitdiff
path: root/baserock_storyboard
diff options
context:
space:
mode:
authorSam Thursfield <sam.thursfield@codethink.co.uk>2014-11-21 19:15:57 +0000
committerSam Thursfield <sam.thursfield@codethink.co.uk>2014-11-21 19:18:24 +0000
commitaa9ff26ce56f1beb642f4eafdec95ce295f48f43 (patch)
tree9500be014db8b065bee399a1ad163c38460fc0c1 /baserock_storyboard
parent326b62ce95705c0e8c8b31259c4962fe1c9db273 (diff)
downloadinfrastructure-aa9ff26ce56f1beb642f4eafdec95ce295f48f43.tar.gz
Work around a Packer bug when deploying development images
Issue is: <https://github.com/mitchellh/packer/issues/1656>. The problem only exists in Red Hat-based operating systems, because for some reason 'cp' gets aliased to 'cp -i', and for some reason Packer doesn't clean up the temporary shell scripts it creates in the system or use 'cp -f' to overwrite them. As a workaround, use '/bin/sh' instead of '/bin/bash' as the shell for Docker deployments, which I think is an improvement in general because the less clever shell code involved in deploying a system the better.
Diffstat (limited to 'baserock_storyboard')
-rw-r--r--baserock_storyboard/packer_template.json3
1 files changed, 2 insertions, 1 deletions
diff --git a/baserock_storyboard/packer_template.json b/baserock_storyboard/packer_template.json
index b5be4c9d..0c735f90 100644
--- a/baserock_storyboard/packer_template.json
+++ b/baserock_storyboard/packer_template.json
@@ -4,7 +4,8 @@
"name": "development",
"type": "docker",
"image": "fedora:20",
- "commit": true
+ "commit": true,
+ "run_command": ["-d", "-i", "-t", "{{.Image}}", "/bin/sh"]
}
],
"provisioners": [