88dc842729
As of April 1, Docker Hub rate limits tightened. With only 10 pulls/hr/IP, we're likely to encounter test failures. Switch all Docker images getting pulled from this repository to use the HashiCorp managed registry mirror. Note that most of our tests in `drivers/docker` don't pull from the remote registry but load a local image, while others will need to pull from the remote and fetch different images depending on OS/arch. Refactor the definition of test task configuration to make it clear which is which, and de-factor some false sharing of setup functions. Updates the E2E tests to use that registry by configuring the Docker daemon. This required changing out a few container images that we don't have in the registry, but these new images are all smaller. There are a couple of tests that still use explicitly-tagged `docker.io` images or other third-party registries, which have been left in place. Ref: https://hashicorp.atlassian.net/browse/NET-12233 update E2E images to those in the registry mirror fix windows and docklog test build fix stopsignal test mop-up more mop-up
Packer Builds
These builds are run as-needed to update the AMIs used by the end-to-end test infrastructure.
What goes here?
- steps that aren't specific to a given Nomad build: ex. all Linux instances
need
jqandawscli. - steps that aren't specific to a given EC2 instance: nothing that includes an IP address.
- steps that infrequently change: the version of Consul or Vault we ship.
How is this used?
The AMIs built by these Packer configs are tagged with BuilderSha, which has
the value of the most recent commit that touched this directory.
The nightly E2E job runs a script to see if there are any AMIs that match the most recent commit that touched this directory, and if there aren't it will then build the AMIs. Then most recent AMI with a matching SHA is used for the nightly E2E run.
If you are changing this directory to build an AMI for testing, it's recommended that you change the name of the AMI or make sure that you've locally committed your changes so that your test AMI doesn't get picked up in the next nightly E2E run.
Running Packer builds
$ packer --version
1.6.4
# build Ubuntu Jammy AMI
$ ./build ubuntu-jammy-amd64
# build Windows AMI
$ ./build windows-2016-amd64
Debugging Packer Builds
To debug a Packer build
you'll need to pass the -debug and -on-error flags. You can then ssh into
the instance using the ec2_amazon-ebs.pem file that Packer drops in this
directory.
Packer doesn't have a cleanup command if you've run -on-error=abort. So when
you're done, clean up the machine by looking for "Packer" in the AWS console: