Unraid Deployment

Unraid Deployment

Unraid normally owns appdata as nobody:users:

• UID 99
• GID 100

PalCenter supports this ownership model without running as root or changing host ownership.

Container settings

Setting	Container value	Suggested host value
Repository	ghcr.io/shanebionic/palcenter:v1.1.1	—
Web UI port	3000/tcp	3000 or another available port
API port	3001/tcp	Optional; restrict to the management network
Persistent data	/app/data	/mnt/user/appdata/palcenter
Container user	99:100	Unraid nobody:users

Add this to Extra Parameters:

--user=99:100

For Compose on Unraid, use:

PALCENTER_UID=99
PALCENTER_GID=100

Appdata

Create or select:

/mnt/user/appdata/palcenter

Map it read/write to /app/data. Do not map Palworld save directories or the Docker socket.

PalCenter verifies that the directory is writable at startup. If the host does not permit permission tightening but the directory remains usable, PalCenter logs a warning and continues. If UID 99 and GID 100 cannot write, startup fails safely.

First start

1. Start the container.
2. Open http://UNRAID-IP:WEB-PORT.
3. Create the first Administrator.
4. Add a Palworld server using a LAN IP or DNS name reachable from the container.

Do not use localhost for a remote Palworld server.

Upgrades and backups

Keep the appdata mapping and --user=99:100 when recreating the container. Create a PalCenter backup before upgrades. For a cold backup, stop the container and copy the complete appdata directory; never copy only a live SQLite file.