From edc8eabe2e34cc16ba5f3060fa1c5122dda2c144 Mon Sep 17 00:00:00 2001 From: Justin Reagor Date: Sun, 21 May 2017 14:40:36 -0400 Subject: [PATCH] Note documentation when building images under private Triton --- website/source/docs/builders/triton.html.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/website/source/docs/builders/triton.html.md b/website/source/docs/builders/triton.html.md index c7a0c1f26..68a661b73 100644 --- a/website/source/docs/builders/triton.html.md +++ b/website/source/docs/builders/triton.html.md @@ -30,6 +30,13 @@ This reusable image can then be used to launch new machines. The builder does *not* manage images. Once it creates an image, it is up to you to use it or delete it. +~> **Private installations of Triton must have custom images enabled!** To use +the Triton builder with a private/on-prem installation of Joyent's Triton +software, you'll need an operator to manually +[enable custom images](https://docs.joyent.com/private-cloud/install/image-management) +after installing Triton. This is not a requirement for Joyent's public cloud +offering of Triton. + ## Configuration Reference There are many configuration options available for the builder. They are @@ -110,7 +117,7 @@ builder. added to the source machine used for creating the image. For example if any of the provisioners which are run need Internet access you will need to add the UUID's of the appropriate networks here. If this is not specified, - instances will be placed into the default Triton public and internal + instances will be placed into the default Triton public and internal networks. - `source_machine_tags` (object of key/value strings) - Tags applied to the VM used to create the image.