|
|
|
|
@ -1,9 +1,9 @@
|
|
|
|
|
//go:generate struct-markdown
|
|
|
|
|
|
|
|
|
|
// The chroot package is able to create an Amazon AMI without requiring
|
|
|
|
|
// the launch of a new instance for every build. It does this by attaching
|
|
|
|
|
// and mounting the root volume of another AMI and chrooting into that
|
|
|
|
|
// directory. It then creates an AMI from that attached drive.
|
|
|
|
|
// The chroot package is able to create an Amazon AMI without requiring the
|
|
|
|
|
// launch of a new instance for every build. It does this by attaching and
|
|
|
|
|
// mounting the root volume of another AMI and chrooting into that directory.
|
|
|
|
|
// It then creates an AMI from that attached drive.
|
|
|
|
|
package chroot
|
|
|
|
|
|
|
|
|
|
import (
|
|
|
|
|
@ -23,111 +23,114 @@ import (
|
|
|
|
|
// The unique ID for this builder
|
|
|
|
|
const BuilderId = "mitchellh.amazon.chroot"
|
|
|
|
|
|
|
|
|
|
// Config is the configuration that is chained through the steps and
|
|
|
|
|
// settable from the template.
|
|
|
|
|
// Config is the configuration that is chained through the steps and settable
|
|
|
|
|
// from the template.
|
|
|
|
|
type Config struct {
|
|
|
|
|
common.PackerConfig `mapstructure:",squash"`
|
|
|
|
|
AMIMappings awscommon.BlockDevices `mapstructure:"ami_block_device_mappings" required:"false"`
|
|
|
|
|
LaunchMappings awscommon.BlockDevices `mapstructure:"launch_block_device_mappings" required:"false"`
|
|
|
|
|
awscommon.AMIConfig `mapstructure:",squash"`
|
|
|
|
|
awscommon.AccessConfig `mapstructure:",squash"`
|
|
|
|
|
// This is a list of devices to
|
|
|
|
|
// mount into the chroot environment. This configuration parameter requires
|
|
|
|
|
// some additional documentation which is in the Chroot
|
|
|
|
|
// Mounts section. Please read that section for more
|
|
|
|
|
// Add one or more block device mappings to the AMI. These will be attached
|
|
|
|
|
// when booting a new instance from your AMI. To add a block device during
|
|
|
|
|
// the Packer build see launch_block_device_mappings below. Your options
|
|
|
|
|
// here may vary depending on the type of VM you use. See the BlockDevices
|
|
|
|
|
// documentation for fields.
|
|
|
|
|
AMIMappings BlockDevices `mapstructure:"ami_block_device_mappings" required:"false"`
|
|
|
|
|
// Add one or more block device mappings to the AMI. These will be attached
|
|
|
|
|
// when booting a new instance from your AMI. To add a block device during
|
|
|
|
|
// the Packer build see launch_block_device_mappings below. Your options
|
|
|
|
|
// here may vary depending on the type of VM you use. See the BlockDevices
|
|
|
|
|
// documentation for fields.
|
|
|
|
|
LaunchMappings BlockDevices `mapstructure:"launch_block_device_mappings" required:"false"`
|
|
|
|
|
// This is a list of devices to mount into the chroot environment. This
|
|
|
|
|
// configuration parameter requires some additional documentation which is
|
|
|
|
|
// in the Chroot Mounts section. Please read that section for more
|
|
|
|
|
// information on how to use this.
|
|
|
|
|
ChrootMounts [][]string `mapstructure:"chroot_mounts" required:"false"`
|
|
|
|
|
// How to run shell commands. This defaults to
|
|
|
|
|
// {{.Command}}. This may be useful to set if you want to set environmental
|
|
|
|
|
// variables or perhaps run it with sudo or so on. This is a configuration
|
|
|
|
|
// template where the .Command variable is replaced with the command to be
|
|
|
|
|
// run. Defaults to {{.Command}}.
|
|
|
|
|
// How to run shell commands. This defaults to {{.Command}}. This may be
|
|
|
|
|
// useful to set if you want to set environmental variables or perhaps run
|
|
|
|
|
// it with sudo or so on. This is a configuration template where the
|
|
|
|
|
// .Command variable is replaced with the command to be run. Defaults to
|
|
|
|
|
// {{.Command}}.
|
|
|
|
|
CommandWrapper string `mapstructure:"command_wrapper" required:"false"`
|
|
|
|
|
// Paths to files on the running EC2
|
|
|
|
|
// instance that will be copied into the chroot environment prior to
|
|
|
|
|
// provisioning. Defaults to /etc/resolv.conf so that DNS lookups work. Pass
|
|
|
|
|
// an empty list to skip copying /etc/resolv.conf. You may need to do this
|
|
|
|
|
// if you're building an image that uses systemd.
|
|
|
|
|
// Paths to files on the running EC2 instance that will be copied into the
|
|
|
|
|
// chroot environment prior to provisioning. Defaults to /etc/resolv.conf
|
|
|
|
|
// so that DNS lookups work. Pass an empty list to skip copying
|
|
|
|
|
// /etc/resolv.conf. You may need to do this if you're building an image
|
|
|
|
|
// that uses systemd.
|
|
|
|
|
CopyFiles []string `mapstructure:"copy_files" required:"false"`
|
|
|
|
|
// The path to the device where the root volume of
|
|
|
|
|
// the source AMI will be attached. This defaults to "" (empty string), which
|
|
|
|
|
// forces Packer to find an open device automatically.
|
|
|
|
|
// The path to the device where the root volume of the source AMI will be
|
|
|
|
|
// attached. This defaults to "" (empty string), which forces Packer to
|
|
|
|
|
// find an open device automatically.
|
|
|
|
|
DevicePath string `mapstructure:"device_path" required:"false"`
|
|
|
|
|
// When we call the mount command (by default
|
|
|
|
|
// mount -o device dir), the string provided in nvme_mount_path will
|
|
|
|
|
// replace device in that command. When this option is not set, device in
|
|
|
|
|
// 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 and device_path.
|
|
|
|
|
// When we call the mount command (by default mount -o device dir), the
|
|
|
|
|
// string provided in nvme_mount_path will replace device in that command.
|
|
|
|
|
// When this option is not set, device in 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 and device_path.
|
|
|
|
|
NVMEDevicePath string `mapstructure:"nvme_device_path" required:"false"`
|
|
|
|
|
// Build a new volume instead of starting from an
|
|
|
|
|
// existing AMI root volume snapshot. Default false. If true, source_ami
|
|
|
|
|
// is no longer used and the following options become required:
|
|
|
|
|
// ami_virtualization_type, pre_mount_commands and root_volume_size. The
|
|
|
|
|
// below options are also required in this mode only:
|
|
|
|
|
// Build a new volume instead of starting from an existing AMI root volume
|
|
|
|
|
// snapshot. Default false. If true, source_ami is no longer used and the
|
|
|
|
|
// following options become required: ami_virtualization_type,
|
|
|
|
|
// pre_mount_commands and root_volume_size. The below options are also
|
|
|
|
|
// required in this mode only:
|
|
|
|
|
FromScratch bool `mapstructure:"from_scratch" required:"false"`
|
|
|
|
|
// Options to supply the mount command
|
|
|
|
|
// when mounting devices. Each option will be prefixed with -o and supplied
|
|
|
|
|
// to the mount command ran by Packer. Because this command is ran in a
|
|
|
|
|
// shell, user discretion is advised. See this manual page for the mount
|
|
|
|
|
// command for valid file
|
|
|
|
|
// Options to supply the mount command when mounting devices. Each option
|
|
|
|
|
// will be prefixed with -o and supplied to the mount command ran by
|
|
|
|
|
// Packer. Because this command is ran in a shell, user discretion is
|
|
|
|
|
// advised. See this manual page for the mount command for valid file
|
|
|
|
|
// system specific options.
|
|
|
|
|
MountOptions []string `mapstructure:"mount_options" required:"false"`
|
|
|
|
|
// The partition number containing the /
|
|
|
|
|
// partition. By default this is the first partition of the volume, (for
|
|
|
|
|
// example, xvda1) but you can designate the entire block device by setting
|
|
|
|
|
// "mount_partition": "0" in your config, which will mount xvda instead.
|
|
|
|
|
// The partition number containing the / partition. By default this is the
|
|
|
|
|
// first partition of the volume, (for example, xvda1) but you can
|
|
|
|
|
// designate the entire block device by setting "mount_partition": "0" in
|
|
|
|
|
// your config, which will mount xvda instead.
|
|
|
|
|
MountPartition string `mapstructure:"mount_partition" required:"false"`
|
|
|
|
|
// The path where the volume will be mounted. This is
|
|
|
|
|
// where the chroot environment will be. This defaults to
|
|
|
|
|
// The path where the volume will be mounted. This is where the chroot
|
|
|
|
|
// environment will be. This defaults to
|
|
|
|
|
// /mnt/packer-amazon-chroot-volumes/{{.Device}}. This is a configuration
|
|
|
|
|
// template where the .Device variable is replaced with the name of the
|
|
|
|
|
// device where the volume is attached.
|
|
|
|
|
MountPath string `mapstructure:"mount_path" required:"false"`
|
|
|
|
|
// As pre_mount_commands, but the
|
|
|
|
|
// commands are executed after mounting the root device and before the extra
|
|
|
|
|
// mount and copy steps. The device and mount path are provided by
|
|
|
|
|
// {{.Device}} and {{.MountPath}}.
|
|
|
|
|
// As pre_mount_commands, but the commands are executed after mounting the
|
|
|
|
|
// root device and before the extra mount and copy steps. The device and
|
|
|
|
|
// mount path are provided by {{.Device}} and {{.MountPath}}.
|
|
|
|
|
PostMountCommands []string `mapstructure:"post_mount_commands" required:"false"`
|
|
|
|
|
// A series of commands to execute
|
|
|
|
|
// after attaching the root volume and before mounting the chroot. This is not
|
|
|
|
|
// required unless using from_scratch. If so, this should include any
|
|
|
|
|
// partitioning and filesystem creation commands. The path to the device is
|
|
|
|
|
// provided by {{.Device}}.
|
|
|
|
|
// A series of commands to execute after attaching the root volume and
|
|
|
|
|
// before mounting the chroot. This is not required unless using
|
|
|
|
|
// from_scratch. If so, this should include any partitioning and filesystem
|
|
|
|
|
// creation commands. The path to the device is provided by {{.Device}}.
|
|
|
|
|
PreMountCommands []string `mapstructure:"pre_mount_commands" required:"false"`
|
|
|
|
|
// The root device name. For example, xvda.
|
|
|
|
|
RootDeviceName string `mapstructure:"root_device_name" required:"false"`
|
|
|
|
|
// The size of the root volume in GB for the
|
|
|
|
|
// chroot environment and the resulting AMI. Default size is the snapshot size
|
|
|
|
|
// of the source_ami unless from_scratch is true, in which case this
|
|
|
|
|
// field must be defined.
|
|
|
|
|
// The size of the root volume in GB for the chroot environment and the
|
|
|
|
|
// resulting AMI. Default size is the snapshot size of the source_ami
|
|
|
|
|
// unless from_scratch is true, in which case this field must be defined.
|
|
|
|
|
RootVolumeSize int64 `mapstructure:"root_volume_size" required:"false"`
|
|
|
|
|
// The type of EBS volume for the chroot
|
|
|
|
|
// environment and resulting AMI. The default value is the type of the
|
|
|
|
|
// source_ami, unless from_scratch is true, in which case the default
|
|
|
|
|
// value is gp2. You can only specify io1 if building based on top of a
|
|
|
|
|
// source_ami which is also io1.
|
|
|
|
|
// The type of EBS volume for the chroot environment and resulting AMI. The
|
|
|
|
|
// default value is the type of the source_ami, unless from_scratch is
|
|
|
|
|
// true, in which case the default value is gp2. You can only specify io1
|
|
|
|
|
// if building based on top of a source_ami which is also io1.
|
|
|
|
|
RootVolumeType string `mapstructure:"root_volume_type" required:"false"`
|
|
|
|
|
// The source AMI whose root volume will be copied and
|
|
|
|
|
// provisioned on the currently running instance. This must be an EBS-backed
|
|
|
|
|
// AMI with a root volume snapshot that you have access to. Note: this is not
|
|
|
|
|
// used when from_scratch is set to true.
|
|
|
|
|
// The source AMI whose root volume will be copied and provisioned on the
|
|
|
|
|
// currently running instance. This must be an EBS-backed AMI with a root
|
|
|
|
|
// volume snapshot that you have access to. Note: this is not used when
|
|
|
|
|
// from_scratch is set to true.
|
|
|
|
|
SourceAmi string `mapstructure:"source_ami" required:"true"`
|
|
|
|
|
// Filters used to populate the source_ami
|
|
|
|
|
// field. Example:
|
|
|
|
|
// Filters used to populate the source_ami field. Example:
|
|
|
|
|
//
|
|
|
|
|
//
|
|
|
|
|
// ``` json
|
|
|
|
|
// {
|
|
|
|
|
// "source_ami_filter": {
|
|
|
|
|
// "filters": {
|
|
|
|
|
// "virtualization-type": "hvm",
|
|
|
|
|
// "name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*",
|
|
|
|
|
// "root-device-type": "ebs"
|
|
|
|
|
// },
|
|
|
|
|
// "owners": ["099720109477"],
|
|
|
|
|
// "most_recent": true
|
|
|
|
|
// "filters": {
|
|
|
|
|
// "virtualization-type": "hvm",
|
|
|
|
|
// "name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*",
|
|
|
|
|
// "root-device-type": "ebs"
|
|
|
|
|
// },
|
|
|
|
|
// "owners": ["099720109477"],
|
|
|
|
|
// "most_recent": true
|
|
|
|
|
// }
|
|
|
|
|
// }
|
|
|
|
|
// ```
|
|
|
|
|
@ -157,13 +160,12 @@ type Config struct {
|
|
|
|
|
// criteria provided in `source_ami_filter`; this pins the AMI returned by the
|
|
|
|
|
// filter, but will cause Packer to fail if the `source_ami` does not exist.
|
|
|
|
|
SourceAmiFilter awscommon.AmiFilterOptions `mapstructure:"source_ami_filter" required:"false"`
|
|
|
|
|
// Tags to apply to the
|
|
|
|
|
// volumes that are *launched*. This is a [template
|
|
|
|
|
// Tags to apply to the volumes that are *launched*. This is a [template
|
|
|
|
|
// engine](/docs/templates/engine.html), see [Build template
|
|
|
|
|
// data](#build-template-data) for more information.
|
|
|
|
|
RootVolumeTags awscommon.TagMap `mapstructure:"root_volume_tags" required:"false"`
|
|
|
|
|
// what architecture to use when registering the
|
|
|
|
|
// final AMI; valid options are "x86_64" or "arm64". Defaults to "x86_64".
|
|
|
|
|
// what architecture to use when registering the final AMI; valid options
|
|
|
|
|
// are "x86_64" or "arm64". Defaults to "x86_64".
|
|
|
|
|
Architecture string `mapstructure:"ami_architecture" required:"false"`
|
|
|
|
|
|
|
|
|
|
ctx interpolate.Context
|
|
|
|
|
@ -289,8 +291,8 @@ func (b *Builder) Prepare(raws ...interface{}) ([]string, error) {
|
|
|
|
|
}
|
|
|
|
|
if len(b.config.AMIMappings) > 0 && b.config.RootDeviceName != "" {
|
|
|
|
|
if b.config.RootVolumeSize == 0 {
|
|
|
|
|
// Although, they can specify the device size in the block device mapping, it's easier to
|
|
|
|
|
// be specific here.
|
|
|
|
|
// Although, they can specify the device size in the block
|
|
|
|
|
// device mapping, it's easier to be specific here.
|
|
|
|
|
errs = packer.MultiErrorAppend(
|
|
|
|
|
errs, errors.New("root_volume_size is required if ami_block_device_mappings is specified"))
|
|
|
|
|
}
|
|
|
|
|
|