From 82aadb3fe20cbf0400ea8e070f9bc978199bda51 Mon Sep 17 00:00:00 2001 From: Megan Marsh Date: Thu, 3 Jan 2019 10:21:41 -0800 Subject: [PATCH] add note about ansible to chroot builder --- website/source/docs/builders/amazon-chroot.html.md | 5 +++++ website/source/docs/provisioners/ansible.html.md | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/website/source/docs/builders/amazon-chroot.html.md b/website/source/docs/builders/amazon-chroot.html.md index 6af73d0a5..24622e049 100644 --- a/website/source/docs/builders/amazon-chroot.html.md +++ b/website/source/docs/builders/amazon-chroot.html.md @@ -455,6 +455,11 @@ services: } ``` +### Ansible provisioner + +Running ansible against `amazon-chroot` requires changing the Ansible connection +to chroot and running Ansible as root/sudo. + ### Using Instances with NVMe block devices. In C5, C5d, M5, and i3.metal instances, EBS volumes are exposed as NVMe block diff --git a/website/source/docs/provisioners/ansible.html.md b/website/source/docs/provisioners/ansible.html.md index 04b7134f2..440215b8a 100644 --- a/website/source/docs/provisioners/ansible.html.md +++ b/website/source/docs/provisioners/ansible.html.md @@ -195,7 +195,7 @@ Redhat / CentOS builds have been known to fail with the following error due to ### chroot communicator Building within a chroot (e.g. `amazon-chroot`) requires changing the Ansible -connection to chroot. +connection to chroot and running Ansible as root/sudo. ``` json {