Oh! That is different then. I'll check it later on.

any chance of a Romestead dedicated server? just started playing it and its quite fun..

On 6/28/2026 at 8:09 PM, Nodiaque said:

Oh! That is different then. I'll check it later on.

The new update was pushed, with the Linux based version for docker, any chance you might be pushing a new version?

Eventually I'm planning to check that. I'm away for 2 weeks and I hope my health get better so I can get back on stuff like this.

1 hour ago, Nodiaque said:

Eventually I'm planning to check that. I'm away for 2 weeks and I hope my health get better so I can get back on stuff like this.

No problem at all, thanks for the reply, and get well!

On 6/28/2026 at 7:26 PM, Drider said:

I think the question is being asked because a new update is around the corner that is going to now support/Add Docker Images with Linux server support.

Windrose - Patch Notes, version: 0.10.0.7 - Steam News

Patch Notes, version: 0.10.0.7

Linux Dedicated Server Support + Small Improvements

Hey, everyone!

We are releasing another batch of small improvements and fixes for the current build.

Please note that we'll also be performing some backend maintenance, which means the game will be temporarily unavailable. We apologize for the inconvenience and appreciate your patience.

Patch notes, version: 0.10.0.7

• Added Docker images with Linux server support. For setup instructions, see DedicatedServer.md in the dedicated server root directory.

• Added Traditional Chinese language support.

• Sails can once again be damaged by cannonball hits.

P.S. Another development blog is coming soon. Stay tuned!

So I guess the question should've been, Will you be updating/adding the docker for the full Linux version that may avoid the need for WINE, and possibly reduce overhead / increase server performance?

I for one would prefer to use your container if so, as I've had near zero issues with your Dockers

OK so I've checked that. What they release is a dedicated docker image built by them on repo windroseserver/windroseserver:latest. We could use that, problem is we cannot change the user. They run everything under the user ue_user and everything is under /home/ue_user/app. Because of that, if we set --user=99:100, it break.

They didn't release anything to create our own linux server beside that. I'm trying to understand how the docker one they release work and see if it's simply running wine like we are doing.

edit: Ok so far, I've manage to understand what they did. The problem is the source file aren't on steam. I could extract them directly from their own docker and have it run, problem will be each update will require a manual job (new image) which will mean having a maintainer. I'll continue investigating.

Edited July 24Jul 24 by Nodiaque

Ok, so I made a new template. Windrose-Linux.

This docker is totally different then the current Windrose one.

Windrose didn't release the Linux dedicated server into steamcmd. The only way to get the file are to extract them from their own docker. We could use their docker directly, but that docker doesn't run as 99:100 user which break unraid.

So what I did is I extracted the docker, copied the server files, checked the dockerfile from the original docker and made it unraid compatible.

Because of that, this docker doesn't auto-update with SteamCMD (it doesn't use SteamCMD at all). I will need to extract each time and create a new docker version, thus update won't be as fast for sure.

Since I do not own the game, I haven't tested. According to log, everything seems to run fine. Migration should be as easy as starting the game, stopping, copying the config file and the save folder. DO NOT MAP DIRECTLY TO THE OTHER CONTAINER.

You will have to create the config file (can be an empty file) before starting, else it will create a folder and crash.

This docker contain all of the game, so it's bigger (~5gb) and you only have the savegame and the config file in appdata.

Edited July 24Jul 24 by Nodiaque

None of what you wrote regarding the "new" Windrose container sounds better than what you had already put together for us months ago.

I'll stick with yours.

9 minutes ago, CoZ said:

None of what you wrote regarding the "new" Windrose container sounds better than what you had already put together for us months ago.

I'll stick with yours.

That's why I made it a different container. Some might want to go to the Linux container instead of wine compatibility layer. I just really don't like how they did it. I never saw a game company release a docker and not use the distribution mechanic. I open a ticket with them asking to push the Linux server on steam like they did with Windows.

21 minutes ago, Nodiaque said:

That's why I made it a different container. Some might want to go to the Linux container instead of wine compatibility layer. I just really don't like how they did it. I never saw a game company release a docker and not use the distribution mechanic. I open a ticket with them asking to push the Linux server on steam like they did with Windows.

Well, let's hope they listen and, follow through.

7 hours ago, Nodiaque said:

That's why I made it a different container. Some might want to go to the Linux container instead of wine compatibility layer. I just really don't like how they did it. I never saw a game company release a docker and not use the distribution mechanic. I open a ticket with them asking to push the Linux server on steam like they did with Windows.

Maybe what he's done here can shed some light. Maybe you can build off his Image?
pfeiffermax/windrose-dedicated-server - Docker Image
The Nerdy Tech Blog

I tried my damnest to get a docker working from his, but I've honestly never setup a docker outside of Community Apps, and I just didn't have the time to invest learning what the hell I'm doing.

He's gotten it set up where his docker will update, as long as Kraken Express pushes updates to the Linux distro (Which it looks like they are maintaining). I'm confident they will eventually set a SteamCMD distro, its' just a question of when.

"My automation checks the Windrose official Image build every night. If a new Image was published by Kraken Express, a new Docker image will be built with this new version. Just use the latest tag and you will always have an up-to-date Docker image. No need to manually run any server updates and mess around with your Docker image. It's that simple. "

I personally am interested in a Linux binary without the WINE on top purely because of server resources. Just as an example, Running a Palworld Docker, (which is very similar to WR), in pure Linux Binaries vs Wine is a night and day difference when it come to resources. I'm hoping to see a similar difference with Windrose.

Edited July 24Jul 24 by Drider
grammar

Yeah he's doing exactly the same as me but he automated it. I'm not very github / docker knowledable so I know nothing about automation.

What he does is the automation check nightly if a new windroseserver/windroseserver docker image is built. If yes, import, extract /home/ue_user/app/ (where all the linux binary are) and then copy them into it's image. It's what I'm going but manually. We both use a debian-trixie image and we even have many things in comon on how our image are built. Maybe he looked at ich777 original work (or the one he based it off). In the end, it's not rocket science for that.

He also start directly with debian-trixie-slim and build from there. while I start from a custom debian image ich777 keep updated (I have made mine but since I have nothing to keep everything updated automatically or simply notify, I still use his). Those "custom" image are tailored for Unraid thus better anyway (respect uid and guid as parameters, properly set permission on run, etc).

edit: Restarting his docker (netdy tech blog) won't update your binary when looking at the code in github.

Automated Docker Image Builds

I built an automation which checks the Windrose public branch every night. If a new release was published by Kraken Express, a new Docker image will be built with this new version. Just use the latest tag and you will always have an up-to-date Docker image. No need to manually run any server updates and mess around with your Docker image.

It's a new docker image, so it's more then restart, you have to update the image, just like any normal docker image.

edit 2: I did learn from his docker though. I didn't think I could copy files directly from another docker in a dockerfile. I'm currently testing it out. If it work, I'll have to learn automation for the next. Thing is now, how I find version since I was doing it manually.

edit 3: Well it work, so it make updating the image much easier and faster. I read on the automation in github and my head hurt so I haven't got anywhere for now. I'm thinking I could do a fetch at the beginning of the image but this would take a long time at each boot. To be continued

Edited July 24Jul 24 by Nodiaque

On 7/24/2026 at 5:56 PM, Nodiaque said:

edit 2: I did learn from his docker though. I didn't think I could copy files directly from another docker in a dockerfile. I'm currently testing it out. If it work, I'll have to learn automation for the next. Thing is now, how I find version since I was doing it manually.

Yeah, I only linked it as I thought maybe it might give you an idea or two. Glad to hear it did, and look forward to seeing if you can find progress for automation.

Good luck!

you know,.. I was just thinking..

It doesn't' exactly have to be automated updates. Even just that it checks the image for updates, and reports back in the unRaid GUI there's an update available, and gives the user the option to apply update would be enough, (basically, the normal docker update behavior, see image).

Of course automation of image update would be nice, as the host of the sever might not be checking daily, but I personally don't feel entirely necessary, as long as we can run the update process through he GUI, and not have to rebuild the container manually each update.

This is not what I'm talking about. To get what you are talking about is what I'm talking about.

This update feature in unraid is simply a check of your Docker image version vs the current one with the tag you use. Unless I update the image this won't happen. It cannot be something in the image that check if something need to be updated and then it show that. It is a docker subsystem thing.

The problem is updating that image. This is where automation is required else I have to do it manually each time.

Edit: I might have badly explained myself but in the end, what need to be understood is I have no control on what the "apply update" do in unraid. This only trigger docker to download new image.

Edited August 4Aug 4 by Nodiaque

16 minutes ago, Nodiaque said:

Edit: I might have badly explained myself but in the end, what need to be understood is I have no control on what the "apply update" do in unraid. This only trigger docker to download new image.

So,.. If I understand correctly, what you are trying to get working is the "update available" recognition of unRaid, and this to some degree does require automation, so that the GUI can recognize there is indeed an update available?

Sorry I've I'm still misunderstanding, I read your reply like 5 times, trying to get what you're saying. Like I said, I've never built a container, but just installed via CA. Though I do feel like I'm getting to point I may invest to the time to learn how to do this stuff manually, as it might be a skill worth learning, for the future administration of my several servers.

Yeah sorry I'm tired so translating my though in English is fleaky at best.

In unraid, the "update available" is simply a docker webfront. What this does is it check the image in the template (where it says nodiaque/steamcmd:windrose for exemple).

In this exemple, nodiaque/steamcmd:windrose mean:

Repository user nodiaque

Image name steamcmd

Tag windrose

Normally, in docker, you have image done in this way:

Swag/swag:1.0.0

Swag/swag:latest

Etc..

Now, what this does. When you select the app in the unraid store, it download the template (the Gui you use to customize settings when creating the app). This template in the end is like a docker-compose.yaml. When you click add/save/run, you can see it download the image and do a docker run command.

Now, what happen in the background is periodically, unraid check the image docker have (in unraid cli, you can do "docker image list" and see all image downloaded) vs the docker hub registry (or ghcr.io depending on what Docker is used in the template). If the version on docker hub is more recent, it will show "update available". When you click on update, it does the command "docker pull image" where image is the information under the template for the docker hub registry (like nodiaque/steamcmd:windrose).

Now, how is there a new version on docker hub? This is where someone need to create it. We do an image doing "docker build source tag" and then docker push to send the image to Docker hub.

The docker build command require a source, and this is where you build the entire image and also, for us, update the server files from official windrose image.

What I manage to do, with the source git of the other person, is automate the source file. I was doing it by hand but there's command in the dockerfile (used by the docker build command) to fetch file from another Docker directly.

The problem now is to automate the docker build and docker push command when a new official windrose image is done. This is what the other person on git did, this is where I don't know how and need to learn a lot.

Ok, that all makes sense, and I appreciate your explanation in such detail.

I may start diving in to this in the next few weeks, but I'm much farther behind in the learning process as I'd be starting from basics. If I can find anything relevant or helpful, I'll do what I can to offer it up here, in hope that it may also help you in the long run.

Thanks again!

I did read on how to make the automation. One of the problem is a bit of lack of interest on my part. I'm no Github expert and when everything start to require custom yaml and such, I'm like bah, there's surely better way. Since my job doesn't use git, I don't learn it even if I code heavily and at my age, we tend to stop wasting time ;)

I've yet to ask some friend who use git like a second nature to simply teach me. I know they will.

I can say for sure that the only reason I was able to explain the docker build and such process is because I did it not too long ago for this specific Docker. I do know the rest properly, but I don't build docker often so I normally forget and need to read my notes again.