Nodiaque

Ah that could be something, since in bridge mode it put the docker internal ip and this can't be resolve on local network sometime. Nice catch

Normally just restarting the server is enough to update. You can follow inch ways of deleting a specific file to force the update on the server if it's not enough when rebooting. This is a steamcmd issue that always existed for many game. Something it doesn't detect new version

Yeah, the requirement are very high. It's not very optimized. Early access after all s

ah nice if only deleting that is enough

That'S the joy of Steam CMD. I saw that many time with other games. When that happen, I simply delete the folder (but keep savedata and config) so it force a redownload.

did you try switching to host network? it's also the risk with any emulation. It's not a linux native server but a Windows (poor coded) one. So Wine emulation can be a miss

Hello, I think no one tried the xvfb yet since I just created it. I created it because there was issue with crashing (way faster then yours) and connection error on day one and looking at other docker, people used this. But since everything was fixed by the dev by the time I created it, I doubt it's the solution. There's no reason for it to mess with your savefile but I would do a backup of the folder in case. Better ready then sorry. In the end, the only difference is xvfb is a framebuffer system to emulate a display without actually displaying it. It's like a virtual display so the game think there's a display running. It's honestly the first time I used that. Do remember it's a early access game that is 2 days old. Lots of bug can happen. I don't think the version of the docker would change that but it doesn't hurt to try. I don't own the game so I can't say the difference myself.

Haha, it happens ;)

just checked on my other unraid instance and see it. Do you see the other windrose made by someone else?

No it should update automatically. Let me check on my other unraid instance just in case it's my cache that's playing with me

weird, I see it. It's even updated to ask for which version you want

ok, I think something happened to the template, let me check

Ah it's seems the update I did didn't go through to put it back to bridge. I'll check later, maybe I made a mistake

Yeah I think they fixed the network part. There was a lot of people in different threads saying they had connectivity troubles even on Windows.

I've push a new tag and updated the template. There is now a new repo nodiaque/steamcmd:windrose-xvfb for those that would like to try with xvfb to see if there's a change in performance. It might also work as bridge network. I tried today to run the non xvfb in bridge and I don't see the error we had yesterday. Wondering if the dev fixed something

I saw many other docker using xvfb, I think I'll make another version with it. The question is does it make a difference for the performance. Or does it remove the need for bridge network

I'll update the template and doc to reflect that

That would be because of the upnp I think. With host, it use directly the nic of the host which give it full access.

Yeah we all do things differently. The UberDude one use xvbf to create a fake screen, but since Pieper has it working, I think it's something else. Maybe connection block to the relay server? Are you able to run one on windows without any problem?

Ah, I really can't say, I'm just running the server XD. I don't even own the game. Maybe you could check in the dev forum for the game (I think they are mostly active on steam). Did you manage to have a working game? Some other user here are reporting crash problem after the tutorial.

windrose is a highly early access game. The Requirement for the game are quite high even for just 2 player. It's also running on Windows Emulation (Wine) which add a layer

I'm going to try something, it will take some time. I saw in the thread that the game doesn't work properly if there's no screen. Some use xvfb to remove that problem. I'll create a new baseimage with wine and xvfb to test. I never did that so we'll see how it goes

Hello, what docker are we talking about? This thread contain 3 different docker. I guess it's probably Enshrouded, which is kowned to have serious performance problem. You could try to use the proton or the non-proton version to see if it work better.

That's what someone in the thread said.

Oh you could simply go the docker compose way by hand and start the docker. Just like you did the docker pull. He did document everything on its Github. I do see in the steam page other user reporting samething. I also saw so. Where (cant find the page anymore on my cellphone) that if it can't reach the relay server, it will close or do something like it after a timeout. Information isn't that big for the dedicated server right now. And the fact it's upnp to a relay server in Russia with no direct connection, really weird.