Quick start
Install Quasar on one Linux GPU server with its own managed database. Check the requirements, then choose your engine, GPU and storage. For a split control plane, follow Docker installation. To expand an existing instance, use its Add GPU host command.
- Host
- Engine
- GPU
- Storage
- Access
- Result
Where are you deploying Quasar?
This sets sensible defaults later, and decides which container engines are supported here.
Which container engine will run Quasar?
This wizard installs Quasar on Docker or Podman running as root (rootful). Not sure what this machine has? Run this on it:
for e in docker podman; do command -v $e >/dev/null && $e --version; doneWant Quasar to run as an ordinary account instead of root? That is a rootless install: follow Rootless.
Which GPU will run your games?
Complete NVIDIA setup for your engine and platform before deploying. It covers the full graphics driver, Container Toolkit and compatibility checks. The engine-specific commands below follow that setup.
This quick start installs everything on one server. Add more machines later with the instance's Add GPU host command.
Where should Quasar keep things?
Homes hold installed games, saves, settings and user files. Leave room for the games you plan to install, in addition to about 20 GB for container images.
A control-only machine keeps no user homes: they live on the GPU hosts. Its database, certificate and machine state are Docker-managed volumes.
Directory and volume reference
Advanced permissions
Game-file ownership
Game containers drop to this user, so it decides who can read the saves from outside Quasar. It does not change what Quasar's own services run as.
Nothing to choose: a control-only machine runs no games.
How will you reach Quasar?
Quasar needs HTTPS. Gamepads, Escape capture and the microphone all need a secure context. The control plane makes its own certificate.
For example, open https://192.168.1.50:8443. Quasar makes a certificate for this address; follow HTTPS setup to trust it. Your client also needs a direct LAN or VPN route to the GPU host.
The default is direct access with Quasar's managed database. For a reverse proxy, extra certificate names or external Postgres, follow advanced installation.
Nothing to choose: a GPU host reaches its control plane through the enrollment string.
Your install
- Host
- Engine
- Role
- User homes
- Owned by
- Console
- Database
Change the ports
Choose a supported or experimental engine in step 2 to see install commands.
1. Prepare the machine, once
Console mode (games on this machine's own screen) needs more device access: see Device rules. For smoother streams, also set the UDP send buffer.
Podman Quadlet configuration
The seed resolves image tags to immutable digests on first install. No manual substitution is needed.
The seed creates Quasar's recovery actor, which generates every secret and creates the rest. Nothing here writes a Compose file or an .env.
Docker Compose configuration
Save this as compose.yaml, or paste it into Docker Compose, Dockge or Arcane. The seed resolves the tags to immutable digests internally on first install. No manual substitution is needed.
The stack's .env
Add to your config
Goes in . This adds Quasar to a proxy you already run; it does not stand one up.
Before starting
Create the homes and templates directories with the chosen ownership. Do not change ownership of existing user data recursively.
Docker users can save compose.yaml and run docker compose up -d, or use their stack manager. Podman users should save quasar-seed.container in /etc/containers/systemd/, then follow the Quadlet start steps.
Existing installation? Keep its homes, database and machine state. Follow Upgrading before redeploying.
Then open Quasar and continue with Create your account. Prefer to read the whole thing instead? Docker, Podman and Unraid cover the same ground as prose.