-
Notifications
You must be signed in to change notification settings - Fork 0
Docker Installation
Docker is the supported production deployment method for PalCenter v1.1.1.
- Docker Engine or Docker Desktop with Compose support
- A persistent Docker volume or writable bind mount
- An existing Palworld dedicated server with its REST API enabled
- Network access from the PalCenter container to each Palworld REST URL
| Port | Purpose | Recommendation |
|---|---|---|
3000/tcp |
PalCenter web interface | Required; publish to your management network |
3001/tcp |
Direct PalCenter API access | Optional; the web interface proxies API requests internally |
Do not publish either port directly to the public internet. Use a trusted network or an HTTPS reverse proxy.
docker volume create palcenter-data
docker run -d \
--name palcenter \
--restart unless-stopped \
--init \
--user 1000:1000 \
--cap-drop ALL \
--security-opt no-new-privileges:true \
-p 3000:3000 \
-v palcenter-data:/app/data \
ghcr.io/shanebionic/palcenter:v1.1.1Create docker-compose.yml:
services:
palcenter:
image: ghcr.io/shanebionic/palcenter:v1.1.1
container_name: palcenter
user: "${PALCENTER_UID:-1000}:${PALCENTER_GID:-1000}"
init: true
restart: unless-stopped
ports:
- "3000:3000"
volumes:
- palcenter-data:/app/data
cap_drop:
- ALL
security_opt:
- no-new-privileges:true
volumes:
palcenter-data:Start the application:
docker compose up -dOpen http://YOUR-SERVER-IP:3000 and continue with First Run Setup.
All PalCenter data must persist at /app/data. Do not mount Palworld save
files, SteamCMD folders, or the Docker socket into this container.
The container runs as a non-root user and does not take ownership of host storage. For bind mounts, the selected UID/GID must already have read/write access. See Docker Configuration and Unraid Deployment.
PalCenter v1.1.1 · Repository · MIT License
PalCenter v1.1.1
Getting Started
Administration
Deployment
Troubleshooting
Project