d686a51d60
The cloud-init configuration runs on boot, which can result in a race condition between that and service startup. This has caused provisioning failures because Nomad expects the userdata to have configured a host volume directory. Diagnosing this was also compounded by a warning being fired by systemd for the Nomad unit file. * Update the location of the `StartLimitIntervalSec` field to it's post-systemd-230 location. * Ensure that the weekly AMI build is up-to-date to reduce the risk of unexpected system software changes. * Move the host volume to a directory we can set up at AMI build time rather than in userdata. |
||
---|---|---|
.. | ||
README.md | ||
ubuntu-bionic.sh | ||
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.