Server does not seem to start properly with proton launcher inside podman #103
Comments
|
Hey @red15, So now to the problem with the proton image itself. Can you test if you can read the steam query output and get any information back with the proton version? exec inside of enshrouded container: su - enshrouded # when connected as root
python3 -c 'import a2s; print(a2s.info(("127.0.0.1",15637)));'You should get some information about the server - like name, version etc. which indicate the server is up and running. |
Ah good to know I've just been pulling
I've been using the Steam->View->Game Servers tab from my client to verify the responses and switching from proton to wine actually started showing content. So I can confirm it's not something on the network setup (which I'll admit is not very standard)
I've just tested |
|
I updated the proton-ge version to 9-18 and is available with In the log run I hope we get a native linux server, so I can get rid of wine or proton. |
|
Looks like it did something, startup log now ends with : But alas the ServerQuery is still not returning anything: Would it be worth implementing this check as a HEALTHCHECK btw? Might want to ensure it's not really using |
|
well thats a bummer and I'm not sure why and what is causing that issue. There seems to be no clear problem on startup, but maybe hangs when initializing the steam connection. Typically thats the next thing that gets logged at that point. Unfortunately the healthcheck is not that strait forward. I use supervisor - thats the pid 1 - and it manages all subprocesses. Autoupdates, backups etc. I need to think about that. |
Is there an existing issue for this?
Used image version
d97d8c0bb6e0
Used docker compose file or docker command
podman pod create enshrouded # Make a pod to contain both tailscale and enshrouded server containers
podman create --pod enshrouded --name tailscale docker.io/tailscale/tailscale # Has plenty more options irrelevant for this bug
podman volume create ensh # For storing the binary data in a persistent volume
podman create --pod enshrouded --name server -v ensh:/opt/enshrouded -e SERVER_QUERYPORT=15637 -e SERVER_*... -e UPDATE_CRON="..." docker.io/mornedhels/enshrouded-server # Trimmed options here for readability
What you expected to see, versus what you actually saw
The process was started but any network queries seemed not to be answered. I had tcpdump confirm the UDP query packages came in but never got a reply.
Reading the repo I found the original Dockerfile which referenced using wine so I exec into the container and ran the wine setup commands and finally did an
apt install wine-stableand edited the/usr/local/etc/enshrouded/enshrouded-serverscript and replaced theproton runinprefix->wine.Starting the container then I saw pretty much the same output as before with proton but now the network did respond properly.
While running the server and joining I did get some possible performance degradation warnings from the game client when 2 players were connected but possibly this is due to limited CPU performance inside the VM where I ran the container.
Logs from the container
Bad startup
Good startup
The text was updated successfully, but these errors were encountered: