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
How it works
- 01
Book and send access
Book online with your ABN or NZBN. We tell you exactly what access and material we need; the clock starts once we have it.
- 02
We do the work
An experienced employee who specialises in this task works through it, and asks before anything outside the scope.
- 03
Delivered with evidence
You get everything listed on this page, with a written account of what was done.
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
Who it's for
A business running Proxmox that wants containers built to one standard and written down, and wants to be told plainly which of its workloads should be a virtual machine instead.
Questions
How fast is delivery?
Standard delivery is within 8 weekday hours per container. Express delivery — within 5 weekday hours — costs 25% more. The clock pauses while we wait on access or on your keys, so a prerequisite you are putting together never counts against the deadline.
Should this workload be a container or a virtual machine?
A container borrows the kernel from your Proxmox host, which is what makes it start in a second and pack four times denser. It also means anything that loads its own kernel modules, wants its own sysctl values, runs a VPN or firewall product, or serves NFS belongs in a virtual machine, and we will say so before you book rather than after. That one is The Per-VM Setup.
Do you build privileged containers?
Only when you name the workload that needs one and sign an acknowledgement that root inside a privileged container is root on your Proxmox host. Unprivileged is the default and it is what we recommend, because root in one of those is a nobody on the host. Privileged and nested together we will not build at any price, and a virtual machine is the right answer for that.
Can you install our application stack in it?
No, and the container is handed over empty on purpose. A web server is The Web Server Install, a database is The Database Install and Hardening, and a mail stack is The Mail Stack Install, each of which does far more than dropping a package in. Docker or Podman inside a container is a job for a virtual machine, and we will explain why when you ask.
What counts as one container?
One container, one network card, one root volume, one entry in your register. Extra mount points, a folder shared in from the host, or a device passed through are all real things we do, but they are not this fixed price, so raise them and we will size it properly.
Why does a container cost almost as much as a virtual machine?
Because a container is cheaper to run and barely cheaper to build properly. We save the boot wait and the disk resize, then spend it on settling how isolated this thing is, choosing where the filter lives, and writing down what an agent inside it can actually see. The density and the startup speed are real savings for you, and they are not savings in the hour somebody spends building it.
Often booked alongside
- DevOps & Servers
The Brute Force Guardian
Repeated failed logins get the attacker's IP banned at your firewall automatically — a standalone fail2ban setup, with your own addresses whitelisted first so you're never locked out.
A$135 From A$67.50 on a plan
- DevOps & Servers
The CI Runner & Pipeline Setup
Build machines wired into the git platform you already run, with up to three pipelines handed over running green on your own code.
A$354 From A$177 on a plan
- Proxmox Administration
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.
A$249 From A$124.50 on a plan