What you can run on it
The image tracks the stable channel of the official repository, so `apt upgrade` moves you forward without reinstalling the server.
Why on a server rather than a laptop
A fixed address
Containers that must be reachable want a stable IPv4 and a real hostname, not a tunnel that dies with your laptop lid.
Snapshot before the risky deploy
Freeze the whole disk, pull the new image, and roll the machine back in a click if it misbehaves.
The firewall sits in front
Published ports are still closed until you open them in the network firewall, so a misconfigured container is not exposed by accident.
From order to a working Docker
Pick Docker as the image
In the configurator, next to the plan and the region.
Add your SSH key
The server boots with it attached; password login can be off from the start.
Log in and check
`docker compose version` answers before you have installed anything.
Bring your stack up
Copy your compose file across and run it.
Straight answers before you deploy
No. It is the standard Engine with your user in the docker group, which is what most Compose files assume. Rootless can be set up afterwards if you need it.
Keep them apart. A panel wants ports 80 and 443 for itself; if you want both, put the panel on one server and the containers on another.
Ready when you are.
Configure a server now. Your account is created right before payment, with the configuration saved.