As I’ve pointed out before here (and in a formal support request) I found the reason that FreeBSD had some issues with cloud-init before and fixed them – it was a literal one-line change in Digital Ocean’s setup.
FreeBSD has now announced, with 14.1, that they are formally supporting cloudinit – from their release notes (still in process, as 14.1 is in “Release Candidate” status at present): https://www.freebsd.org/releases/14.1R/relnotes/
14.1-RELEASE supports cloudinit, including the nuageinit
startup script and support for a config-drive
partition. It is compatible with OpenStack and many hosting facilities. See the cloud-init web site and the commit messages, 16a6da44e28d 227e7a205edf. (Sponsored by OVHCloud)
Given this will Digital Ocean be restoring FreeBSD as a formal choice? I’ve got it working perfectly-well with 13.x however, other than by cloning an existing droplet I cannot set up new ones with full functionality as using an ISO or cloud image as the base Digital Ocean at present does not permit initializing IPv6, which I need for my uses.
Thanks in advance.
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!
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.
Hey @karldenninger,
I don’t think that there are any officially announced plans for this.
I saw that you’ve already posted this on the DigitalOcean ideas board. I’m sharing a link to the idea here so that other people could find it and upvote and comment as well:
I just upvoted the idea as well.
- Bobby.
Quick data point: I am successfully using FreeBSD up to 14.2 by means of custom images, and everything works fine. Of course I moved the bigger loads to AWS, where FreeBSD support is not a second class citizen.