Windrose-Game-Dedicated-Server is a Docker-based self-hosting solution for running a dedicated server for Windrose, a multiplayer pirate survival game developed by Windrose Studios. The project addresses a common gap for players who want full control over their game environment but lack native Linux server binaries or streamlined setup tooling. Since Windrose is built for Windows and distributed via Steam, hosting a dedicated server outside of Steam’s built-in “host game” option requires Wine, SteamCMD, and manual configuration — tasks this container automates. It packages the official Windrose dedicated server executable (distributed as WindRoseServer.zip in GitHub releases) into a reproducible, isolated environment. The container is maintained by a contributor on GitHub, not the official Windrose team, and carries an MIT license.

What it does
This project delivers a ready-to-run dedicated server container with minimal manual intervention. It is designed specifically for the Windows-based Windrose dedicated server binary, running under Wine inside a Debian-based Docker image. The container handles SteamCMD authentication and updates, mounts persistent storage for world data and configuration, and exposes standard game and query ports. Configuration lives in a standard INI file path that matches Windrose’s expected layout. No custom server code is included — it wraps the official server binary.

  • Runs the official Windrose dedicated server binary under Wine
  • Uses SteamCMD to auto-update the server on container start
  • Supports RCON and admin commands for remote server management
  • Persists world saves and configuration across container restarts
  • Accepts custom ServerSettings.ini via mounted volume at Saved/Config/WindowsServer/

Getting it running
The repository does not include Docker build instructions or a Dockerfile in the provided context, nor does the README show docker run commands. However, based on the project name and description — “Docker container for running a Windrose dedicated server” — users are expected to build or pull a Docker image, then run it with appropriate volume mounts and port mappings. The server binary is provided as a release asset: WindRoseServer.zip. Extraction of that ZIP yields the Windows executable and supporting files needed for the container.

To use it, you would typically:

  1. Download and extract WindRoseServer.zip
  2. Place the extracted folder into a directory (e.g., ./windrose-server/)
  3. Mount that directory as a volume, ensuring Saved/Config/WindowsServer/ServerSettings.ini is present and editable
  4. Map ports 7777 (game) and 7778 (query)
  5. Run the container with --network host or explicit port publishing

No docker-compose.yml is referenced in the provided context, and no ENTRYPOINT or CMD details are visible in the README excerpt. Users need to inspect the actual Dockerfile (if included in the repo) or rely on community examples to construct a working docker run invocation. The container assumes Wine and SteamCMD are pre-installed in its base image — likely built from a Debian or Ubuntu base with Wine 8+ and SteamCMD installed via apt.

Who this is for
This container suits players familiar with Docker and comfortable editing INI files. It is not aimed at beginners who expect one-click installs or GUI configuration. If you run your own homelab or VPS and want a private Windrose server for a small group — say, 4–16 players — and already manage other self-hosted game servers (e.g., Valheim, Rust), this fits. It is also appropriate if you need world persistence, mod support, or custom server rules that the in-game “host game” option does not allow. The container gives you root-level control over the environment: you can add custom DLLs, patch configs before launch, or integrate with log shippers or backup scripts.

How it compares
There are no known official or community-maintained alternatives that package the Windrose dedicated server as a Docker container. Other approaches include running the server natively on Windows (requiring a Windows machine or VM), or using Wine manually on Linux — both of which demand more setup and maintenance. Compared to general-purpose game server managers like LGSM (Linux Game Server Managers), this project is narrower in scope: it does not support multiple games, lacks built-in monitoring or update scheduling, and offers no web dashboard. It is lighter than full game server platforms but heavier than a raw wine ./WindRoseServer.exe script. At 43 GitHub stars and written in C++ (likely reflecting the game’s engine, not the container logic), it remains a niche, community-driven tool — not a production-grade platform.

The project links directly to the official Windrose game but is not affiliated with Windrose Studios. It relies on publicly available server binaries and Steam’s public app ID (not disclosed in the README, but inferable from SteamCMD usage). If you prefer managed hosting or do not run Docker, this container adds unnecessary complexity. It does not support automatic backups, telemetry, or anti-cheat integration. The README shows no CI/CD badges, no issue templates, and no contributor activity timeline — so users should assess maintenance readiness before depending on it long-term.

Source code and release assets are available at https://github.com/puppygirllloll/Windrose-Game-Dedicated-Server.

View on GitHub →