Hi,
I have a droplet image that I boot through the API every now and then. Using cron this droplet executes a number of computing tasks, and when done, shuts itself down (through the API).
However since recently this no longer works. Upon creating the image, the root password that is set by DigitalOcean is expired. This means that the computing tasks that are supposed to start by cron do not run - since they are waiting for the root account password to be unlocked/reset.
So far the only way to get this to work is to actually log in to the server through SSH and set a new root password. This is not something that I like to do as the process of creating, computing and destroying should be automatic.
Is there any way to not have the root password (set by DigitalOcean when creating a droplet from my image) be expired? Or alternatively, change the configuration of the image to ignore the fact that a password is expired - basically allowing cron to run even though the password is expired.
Thanks!
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
If you setup an SSH key pair and supply the the public key when creating the droplet, you will not need to provide or reset the password. This has the added benefit of making your droplet more secure.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.