iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix docs becuase we dont need to actually set the mount path

This commit is contained in:
Megan Marsh 2018-05-23 13:34:56 -07:00
parent b5095539a7
commit 974e464f35
1 changed files with 1 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/source/docs/builders/amazon-chroot.html.md
View File

@ -231,8 +231,7 @@ each category, the available configuration keys are alphabetized.
that command will be something like `/dev/sdf1`, mirroring the attached that command will be something like `/dev/sdf1`, mirroring the attached
device name. This assumption works for most instances but will fail with c5 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 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 instances, you must manually set `nvme_device_path` and `device_path`.
`mount_path`.
- `pre_mount_commands` (array of strings) - A series of commands to execute - `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 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, "ena_support": true,
"ami_name": "amazon-chroot-test-{{timestamp}}", "ami_name": "amazon-chroot-test-{{timestamp}}",
"mount_path": "/mnt/my/mount/path/",
"nvme_device_path": "/dev/nvme1n1p", "nvme_device_path": "/dev/nvme1n1p",
"device_path": "/dev/sdf" "device_path": "/dev/sdf"
} }