00bc6a7d13
Our dnsmasq configuration needs host-specific data that we can't configure in the AMI build. But configuring this in userdata leads to a race between userdata execution, docker.service startup, and dnsmasq.service startup. So rather than letting dnsmasq come up with incorrect configuration and then modifying it after the fact, do the configuration in the service's prestart, and have it kick off a Docker restart when we're done. |
||
---|---|---|
.. | ||
README.md | ||
windows-2016.ps1 |
userdata
These scripts are copied up to instances via Terraform provisioning and
executed once on first boot by
cloud-init
. Userdata scripts
should contain configuration specific to an instance but not configuration
specific to a given deployment of Nomad.