Re:Bring Your Custom Image to DigitalOcean
by 15DCFA8F on Friday October 05, 2018 @06:44PM
(#18152318)
Why only ext3/4 filesystems? Why not XFS?
[ Parent
| on HN ]
Re:Bring Your Custom Image to DigitalOcean
by alexforster on Friday October 05, 2018 @07:31PM
(#18152561)
They likely need to be able to mount your filesystem for some of their features to work. That's how they can reset your root password, write out network configs, etc etc.
Re:Bring Your Custom Image to DigitalOcean
by Operyl on Saturday October 06, 2018 @01:09AM
(#18153645)
Network configs are written out via cloud-init last I checked, hence the requirements on one of the variants.
Also: You must add an SSH key when creating a Droplets from a custom image. These Droplets have password authentication disabled by default and it’s not possible to use the control panel to generate or reset the root password.
https://www.digitalocean.com/docs/images/custom-images/overv...
Re:Bring Your Custom Image to DigitalOcean
by donatj on Friday October 05, 2018 @09:38PM
(#18153009)
Oh that's so lame. I wanted to run something exotic like BeOS or Plan 9. PoorMan in BeOS was the first public webserver I ever ran! Followed shortly by IIS on Windows 2k... Which should also be an option.