From 974e464f356b0446f59878b476db47a78a704063 Mon Sep 17 00:00:00 2001 From: Megan Marsh Date: Wed, 23 May 2018 13:34:56 -0700 Subject: [PATCH] fix docs becuase we dont need to actually set the mount path --- website/source/docs/builders/amazon-chroot.html.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/website/source/docs/builders/amazon-chroot.html.md b/website/source/docs/builders/amazon-chroot.html.md index ce03970ee..9c16fc320 100644 --- a/website/source/docs/builders/amazon-chroot.html.md +++ b/website/source/docs/builders/amazon-chroot.html.md @@ -231,8 +231,7 @@ each category, the available configuration keys are alphabetized. that command will be something like `/dev/sdf1`, mirroring the attached device name. This assumption works for most instances but will fail with c5 and m5 instances. In order to use the chroot builder with c5 and m5 - instances, you must manually set `nvme_device_path`, `device_path`, and - `mount_path`. + instances, you must manually set `nvme_device_path` and `device_path`. - `pre_mount_commands` (array of strings) - A series of commands to execute after attaching the root volume and before mounting the chroot. This is not @@ -437,7 +436,6 @@ A working example for mounting an NVMe device is below: }, "ena_support": true, "ami_name": "amazon-chroot-test-{{timestamp}}", - "mount_path": "/mnt/my/mount/path/", "nvme_device_path": "/dev/nvme1n1p", "device_path": "/dev/sdf" }