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.
A container takes about a second to create, which is why nobody writes down what they gave it. Six months later somebody asks whether that one is privileged, and the answer is a shrug.
We hand you a container that is finished, and unprivileged unless you asked otherwise and told us which workload needed it. It comes up on the address you asked for, takes your keys, refuses everything else, and answers on the ports you chose and no others.
Our engineers have been building Linux servers since 2003, and they will tell you when a workload belongs in a virtual machine instead. You get the output of every check we ran, including proof read back from the host that the container we built is the one you agreed to.
What's included
A container live on the address you asked for, at a size that follows from what you tell us it has to do, so nobody guesses and nobody bills you for a benchmarking exercise
Your keys in, with root and password logins shut, proved by us trying both from a machine you choose and handing you what came back
Only the ports you named answering, filtered on the Proxmox side where your firewall is switched on, so a workload that later turns off its own firewall does not open the door
Unprivileged by default, with what that means for you in writing: what a shared kernel does and does not protect you from, and which workloads we will tell you to put in a virtual machine instead
Up to date the day it is born, with automatic updates left off on purpose and the reason in writing, because an auto-updater that takes a live service down at 4am is nobody's idea of a favour
Reporting into the monitoring you already run, with the honest note that an agent in here sees the container rather than the host, so you are never told you have coverage you do not have
A snapshot of exactly what we handed over with the one line that puts it back, and one entry in a register you keep: what this container is, what it answers on, and how isolated it really is
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, plus storage that accepts containers and the bridge they attach to
Your choice of unprivileged or privileged, and for privileged, the workload that needs it
For each container: its operating system, hostname, timezone, what it is for, and a DHCP or fixed address
Your SSH public keys, the addresses allowed to reach SSH, and up to five other ports to open
A machine on your network we can test the connection from
If you already run monitoring: the server's address and its enrolment key
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 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.
The Proxmox Backup Server Setup
Proxmox Backup Server standing behind every guest on your node or cluster, with one of your machines restored from its backup, booted in front of you and timed before we hand anything over.