SDK/Sandbox requires hostname resolution
Description
Release Notes
None
Activity
Show:
NitinM June 9, 2020 at 1:30 AM
Closing issues that haven't been updated for more than 2 years.
Derek Wood June 20, 2017 at 10:34 PM
New AMIs for the AWS cloud sandbox have been deployed, containing the workaround above.
Leaving this open to either document or remove the requirement.
Derek Wood June 15, 2017 at 8:31 PM
Derek Wood June 15, 2017 at 8:08 PM
I have a workaround to configure cloud-init to manage /etc/hosts. Then at boot time, cloud-init will insert a record for the hostname into /etc/hosts.
before:
after:
I've confirmed the sandbox works in a VPC without private DNS
The only downside is that users wanting to take over management of /etc/hosts would need to disable cloud-init.
Won't Fix
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Bhooshan MogalReporter
Derek WoodComponents
Priority
MajorCreated June 13, 2017 at 1:29 AM
Updated June 9, 2020 at 1:30 AM
Resolved June 9, 2020 at 1:30 AM
The SDK/Sandbox requires the hostname to be resolvable. This can be problematic in the cloud, where instances may not have private DNS. In particular, private DNS hostnames are configurable in an AWS VPC, and our various AMIs may fail to start due to this.
We need to first look into removing this requirement from the java code, else somehow work around it in the various distributions, or at least document.