github.com/hernad/nomad@v1.6.112/e2e/terraform/packer/README.md (about)

     1  # Packer Builds
     2  
     3  These builds are run as-needed to update the AMIs used by the end-to-end test infrastructure.
     4  
     5  
     6  ## What goes here?
     7  
     8  * steps that aren't specific to a given Nomad build: ex. all Linux instances need `jq` and `awscli`.
     9  * steps that aren't specific to a given EC2 instance: nothing that includes an IP address.
    10  * steps that infrequently change: the version of Consul or Vault we ship.
    11  
    12  
    13  ## Running Packer builds
    14  
    15  ```sh
    16  $ packer --version
    17  1.6.4
    18  
    19  # build Ubuntu Jammy AMI
    20  $ ./build ubuntu-jammy-amd64
    21  
    22  # build Windows AMI
    23  $ ./build windows-2016-amd64
    24  ```
    25  
    26  ## Debugging Packer Builds
    27  
    28  To [debug a Packer build](https://www.packer.io/docs/other/debugging.html)
    29  you'll need to pass the `-debug` and `-on-error` flags. You can then ssh into
    30  the instance using the `ec2_amazon-ebs.pem` file that Packer drops in this
    31  directory.
    32  
    33  Packer doesn't have a cleanup command if you've run `-on-error=abort`. So when
    34  you're done, clean up the machine by looking for "Packer" in the AWS console:
    35  * [EC2 instances](https://console.aws.amazon.com/ec2/home?region=us-east-1#Instances:search=Packer;sort=tag:Name)
    36  * [Key pairs](https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#KeyPairs:search=packer;sort=keyName)
    37  * [Security groups](https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#SecurityGroups:search=packer;sort=groupName)