The Cloud-Init Template Library
Four tested starting points for your virtual machines, so a new server is a two-minute clone rather than another operating-system install, and every clone comes up with an identity of its own.
Standing up a server should take two minutes. It takes forty, because somebody is sitting through another operating-system install and then setting the timezone, the keys and the agent again from memory.
We build four templates for the Linux versions you standardise on, each carrying the same defaults: your SSH keys, your timezone and locale, the agent Proxmox needs to see inside a machine, and a root disk that grows to whatever size you give it. Cloning one gets you a running server in about a minute.
We then prove every one of them, cloning each, booting it and checking it against eight things before deleting the test machine. One template we clone twice, so you can watch the two copies come up with identities of their own. Our engineers have been building Linux fleets since 2003.
What's included
Four templates for the Linux versions you actually run, all carrying the same defaults, so a new server becomes a clone and a boot instead of an install and an afternoon
Your SSH keys, your timezone and your locale already inside every one, so a fresh machine is yours from its first boot rather than after twenty minutes of setup
A root filesystem that grows to whatever disk size you ask for at clone time, so a 200 GB machine has 200 GB of usable space without anybody resizing a partition
Every clone with an identity of its own, proved by cloning one template twice so you see two machines come up different. A copied VM hands the same machine ID and SSH host keys to every copy, which is what breaks DHCP leases and makes host-key warnings meaningless
Proxmox able to see inside every machine you clone, so its address shows in the interface and a shutdown request is obeyed instead of pulling the power
All four cloned, booted and checked against eight things before handover, with the results written down and the test machines destroyed
A one-page index of the library, the exact build steps archived so your own team can rebuild any template without us, and a plain note on how they age and how to refresh them
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
Root or sudo SSH access to the Proxmox node we build on, with a route out to the official Linux image mirrors
Your four operating systems from our list, and a size for each
The SSH public keys, login name, timezone and locale every new machine should carry
A storage ID, a network bridge and four free VM IDs for the templates, and whether test clones get their address by DHCP
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Per-VM Setup
A new Linux VM on your own Proxmox, handed over finished: your keys in, root and password logins shut, and only the ports you named answering — each of those proved by trying it from a machine you choose rather than by reading a config file.
The Per-LXC Setup
A new Linux container on your own Proxmox, handed over finished and unprivileged by default: your keys in, root and password logins shut, only the ports you named answering — and the isolation you actually got written down instead of assumed.
The Proxmox Cluster
Three Proxmox servers joined into one cluster with working high availability, proved by deliberately killing a node in a window you choose, so you watch the platform recover before you trust anything to it.
The Linux Server Hardening
One production Linux server closed off at the operating-system level to the break-in routes attackers rely on — with before-and-after evidence of every change we make.