Run a V Rising Dedicated Server in Docker
This guide walks you through running a V Rising dedicated server inside a Docker container, giving you a persistent, isolated, and easily manageable game server. You’ll set up a container with the correct ports, configure the server settings, and learn how to update and back up your world. Before starting, ensure you have Docker installed and a basic understanding of the command line.
What You’ll Need
- Docker installed on your host machine (Docker Engine on Linux, Docker Desktop on Windows/macOS).
- A Steam account with access to V Rising (the server files are free via SteamCMD).
- Basic familiarity with the terminal or command prompt.
- At least 10 GB of free disk space for the server files and world data.
- Open ports 9874 (UDP) and 9875 (UDP) on your router/firewall if you want players outside your local network to join.
Step-by-Step
- Create a directory for your server data. This will hold the server files, settings, and world saves. For example:
mkdir vrising-server && cd vrising-server - Create a
docker-compose.ymlfile. This file defines the container. Use a text editor to create it with the following content:services: vrising: image: trueosiris/vrising:latest container_name: vrising-server restart: unless-stopped environment: - TZ=UTC - SERVERNAME=My V Rising Server - SERVERPORT=9874 - WORLDNAME=MyWorld - SAVEINTERVAL=600 ports: - "9874:9874/udp" - "9875:9875/udp" volumes: - ./server-data:/appAdjust the environment variables to your liking (see Tips for more options).
- Start the server. Run
docker compose up -din the same directory. Docker will pull the image and start the container. - Verify the server is running. Check the logs with
docker compose logs -f. You should see output indicating the server is starting and eventually a message like “Server started on port 9874”. - Connect to your server. In V Rising, go to the server browser, select the “Custom” tab, and enter your server’s IP address and port (default 9874). If you’re playing on the same machine, use
localhost. - Stop the server gracefully. To shut down, run
docker compose stop. This sends a SIGTERM signal, allowing the server to save the world. - Update the server. To update to a new game version, pull the latest image and recreate the container:
docker compose pull && docker compose up -d.
Common Mistakes
- Forgetting to open UDP ports. V Rising uses UDP, not TCP. Ensure both 9874 and 9875 are forwarded on your router and allowed through your firewall.
- Using the wrong port. The default game port is 9874, but the query port is 9875. Some guides mix these up, causing connection issues.
- Not mounting a volume. If you don’t map the
./server-datavolume, all world data is lost when the container is removed. Always use the volume as shown. - Changing settings incorrectly. Editing
ServerHostSettings.jsoninside the container directly is possible, but it’s easier to use environment variables. If you edit the file, restart the container to apply changes.
Tips
- Use environment variables for easy configuration. The
trueosiris/vrisingimage supports many variables likeSERVERNAME,WORLDNAME,SAVEINTERVAL, andMAXUSERS. Check the image’s documentation for a full list. - Set a timezone. Add
TZ=Your/Timezone(e.g.,TZ=America/New_York) to keep server timestamps consistent. - Back up your world regularly. Copy the
server-data/Savesdirectory to a safe location. You can automate this with a cron job or a script. - Use a named volume instead of a bind mount. If you prefer Docker-managed storage, replace
./server-data:/appwithvrising-data:/appand addvolumes: vrising-data:at the end of the compose file. - Monitor resource usage. Use
docker statsto see CPU and memory usage. V Rising is CPU-intensive, so ensure your host has enough cores.
Troubleshooting
- Server doesn’t start. Check the logs with
docker compose logs. Common issues include missing SteamCMD files or insufficient permissions. Try removing theserver-datafolder and starting fresh. - Players can’t connect. Verify the server is running and the ports are open. Test locally with
localhost:9874. If that works, the issue is likely firewall/router configuration. - World resets after restart. This means the volume isn’t mounted correctly. Ensure the
volumes:section in your compose file is correct and the container has write permissions to the directory. - Server appears in the list but shows as “Not Responding”. This is often a query port issue. Make sure port 9875 is also open and not blocked.
- Performance issues. Reduce the
MAXUSERSvariable or lower the game’s graphics settings on the server (though the server doesn’t render graphics). Ensure your host meets the minimum requirements.
Frequently Asked Questions
Can I run multiple servers on one machine?
Yes, you can run multiple containers with different ports and volume directories. Just create separate compose files or use the --project-name flag.
How do I change the server password?
Set the SERVERPASSWORD environment variable in your compose file. Leave it empty for no password.
How do I install mods?
Mods are not officially supported on dedicated servers. Some community mods exist, but they require manual installation into the server files, which may not persist across container updates.
How do I update the server without losing my world?
Your world is stored in the mounted volume, so updating the image won’t delete it. Simply run docker compose pull && docker compose up -d.
Can I use this on Windows?
Yes, Docker Desktop for Windows works, but you must use the WSL2 backend for Linux containers. The commands are the same.
How do I back up my server?
Copy the server-data/Saves folder to a safe location. You can also use docker cp to copy files from the container, but the volume is easier.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.