Self-host Palworld Server with Levelrail
A dedicated Palworld server with a generated admin password and RCON kept internal.
- Memory16 GiB
- Archarm64
- Services1
How to self-host Palworld Server
-
Pull the images
One image is pulled on your server.
Show images
thijsvanloef/palworld-server-docker:v2.8.1
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8211.
-
Fill in the secrets
1 secret is generated and stored encrypted, 4 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Palworld Server requirements
- Memory
- About 16 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8211
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8211 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Palworld Server. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Palworld Server docs page.
Deploy Palworld Server your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Palworld Server from the CLI
levelrail-cli templates deploy palworld --name my-palworld Deploy Palworld Server with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/palworld/deploy Palworld Server configuration
Palworld Server services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| palworld | thijsvanloef/palworld-server-docker:v2.8.1 | 8211 | palworld_data -> /palworld |
Palworld Server environment variables
| Variable | Service | Value |
|---|---|---|
| ADMIN_PASSWORD | palworld | Generated at deploy |
| MULTITHREADING | palworld | Preset by the template |
| PLAYERS | palworld | Preset by the template |
| PORT | palworld | Preset by the template |
| RCON_ENABLED | palworld | Preset by the template |
Ports and volumes
- Ports
- 8211
- Volumes
- 1 named mount: palworld_data -> /palworld
Palworld Server FAQ
How much memory does Palworld Server need?
The catalog lists about 16 GiB of memory for Palworld Server.
Does Palworld Server run on arm64?
For Palworld Server, an arm64 image is published; amd64 is image published.
Does Palworld Server need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Palworld Server use?
Palworld Server listens on port 8211 inside the stack.
Where does Palworld Server keep its data?
In a named volume: palworld_data mounted at /palworld.
Can I deploy Palworld Server on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Palworld Server, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image thijsvanloef/palworld-server-docker:v2.8.1 is what you deploy there.