Comment by mdaniel
7 months ago
Related to the API part, I was browsing and noticed that https://infuze.cloud/docs/api#/Virtual%20Machines/post_vms references templateVMID but https://infuze.cloud/docs/api#/Templates/get_templates shows only "get" so is the template just for quick-start scenarios or users could [eventually] create their own?
Great question. Currently, the templates are pre-configured by us for quick-start scenarios (e.g., Ubuntu 24.04, AlmaLinux, etc.). The API allows you to list these and use them to launch a new VM. The ability for users to create their own custom templates (i.e., take a snapshot of a configured VM and use it as a base image for future deployments) is very high on our roadmap. It's the logical next step after implementing cloud-init support. We see that as a critical feature for building scalable, repeatable infrastructure. So, to answer directly: not yet, but soon.
> (i.e., take a snapshot of a configured VM and use it as a base image for future deployments)
I would advise against that if possible, since the "reset" process for an already contaminated VM is much trickier than the "build-up" process for what one would think of as a template. That's actually why `docker build` exists when `docker save` already exists. I do recognize from your other comments that my mental model may not map onto your target audience, so my comments are always "for your consideration" and not wagging my finger at your choices
If you were to choose to go with "build up," there are already so many specifications for that template construction process you could choose any one of them that you think would work well for your audience: Containerfile[1], Dockerfile, Packer, AWS Image Builder, and probably hundreds of others
1: relevant: bootc-image-builder: Build your entire OS from a Containerfile - https://news.ycombinator.com/item?id=44367004 - June, 2025 (27 comments)