Did DigitalOcean change the way hostnames are set for droplets from custom images?

Posted April 25, 2020 701 views
Custom Images

It used to be the droplet’s name, but now it seems to be the original hostname. I’m running on a mountain pile of errors from my droplets because of that uninformed change.

Iaas should be reliable. The smallest of changes on the infrastructure can create a catastrophe for some operations, even more if it’s uninformed.

If that’s now a new policy, please, first manage to inform the developers that hold operations in DO before making changes on how the infrastructure behave, and secondly, always put an option for people that developed in the old assumptions of the infrastructure.

Unfortunately that small, uninformed change will hold my operation back for weeks.

1 comment
  • After investigating a little further, I realize that only images that have boto3 installed don’t get the hostname equal to it’s name. Is that an expected behavior?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer

Hi there @joseassumpcao,

I had a chat with the support team, and I was informed that the hostnames are generally handled by cloud-init, which in general are pulled from the Droplet name.

It may be pulling this from metadata, but the exact detail would require analyzing (perhaps reviewing the logs at startup) the start-up process to identify what and when is being set.

Cloud-init and boto3 are python packages. I wonder if there is some change to the environment or some dependencies for the cloud-init that changes over that.

In terms of custom images, however, DigitalOcean does not define/specify the behavior. The release of cloud-init software on the Droplet determines that.