By ArchLinux
The image (AMI) building process for Amazon seems different from the rest… Any idea what the real differences are for someone looking to automate image building?
I was hoping to build fresh images like one can do for EC2 like this: https://git.uplinklabs.net/steven/projects/archlinux/ec2/ami-builder-image.git/
How would that be different on DigitalOcean? Installing a distro manually and then imaging it isn’t a nice way I think. I find it strange that DO removed ArchLinux… It shouldn’t be that hard to support, right?
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!
Hi there,
What I have been personally using to automate the image-building process is Packer.
Packer is an open-source tool for creating identical machine images for multiple platforms from a single source configuration. It supports many builders such as AWS, DigitalOcean, GCP, and more. It also supports provisioners, allowing you to install and configure your applications inside the images.
You can find the official Packer documentation here:
https://developer.hashicorp.com/packer/plugins/builders/digitalocean
Here is an example Packer project that I’m using to build the Laravel 1-Click image from the DigitalOcean Marketplace:
Best,
Bobby
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.