Server won't start after patch today. #8
-
|
Hi. I've been using the server without issues pretty much since you first made this. But today I'm having issue getting it started again after todays patch. I'm on Cachyos and it's all been working fine untill I decided to update cachyos today, rebooted and update the pull version to 1.6.2. Here's what the log keeps looping pretty much windrose | usermod: no changes |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
|
Hey, that is not good! Sad to hear that. I will try to help as much as I can. Just to be sure as it says, network is not working. Is it working correctly outside of docker? |
Beta Was this translation helpful? Give feedback.
@BootieTrap what you pasted is enough.
Good news — this is fixable! I can see exactly what is wrong from your output.
Problem 1 — DNS: Your host uses 127.0.0.53 (systemd-resolved stub) as DNS. Docker containers cannot reach that loopback address, so SteamCMD cannot resolve any hostnames. Notice that docker run --dns 8.8.8.8 alpine worked fine — it just needs an explicit DNS server.
First let's try quick fix:
Problem 2 — wine: socket : Function not implemented: This is an AF_ALG socket blocked by seccomp — likely your CachyOS kernel update tightened Docker's seccomp profile. Add this to the same service block in docker-compose.yml