I'm running into a really strange problem with my Docker setup on Windows 11. Whenever I try to create a Satisfactory server container (using the Wolveix image), it causes all the ports on my computer to crash and become unreachable. This happens even if I try to run one server on a different port or just start it alone; once the server reaches the point where it starts listening on its port, everything else stops working until I reboot my machine. I've already double-checked that my firewall is off, and my router settings are correct for port forwarding. Just for context, I usually run Docker Desktop 4.48.0 on Pro version of 25H2. It's worth mentioning that if I run the server outside Docker with SteamCMD, everything works fine. Any ideas on what could be causing this?
5 Answers
I had a similar issue where Docker was jumping to a private IP range that overlapped my local network. Have you set specific network ranges for your Docker stacks? It could help prevent this port issue.
I'm curious why you're trying to run it in Docker when you mentioned it works fine with SteamCMD. Are you thinking about moving to Linux later, or is it just for easier management?
I understand the troubleshooting can be frustrating, especially with overlap issues from WSL2. Have you tried looking into how Docker manages ports? Sometimes it can be tricky – like asking for ports that don’t match expected configurations.
Yeah, I had to stop when it got weird with port requests that weren't actually needed. It made no sense.
Docker on Windows can be problematic. If you haven’t already, consider running it inside a Linux VM instead. It’s generally more efficient and safer without worrying about Windows firewall issues.
Why do you have the memory limits commented out for server 3? Was that a temporary measure? I’m wondering if the other servers were consuming too much memory, affecting performance.
I like using Docker to monitor and manage multiple servers easily. With SteamCMD, I can't easily set different ports for each server which I need.