-
-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Steamcmd states being offline and crashes on image version >= v1.8.0 #306
Comments
What version of Ubuntu are you rubbing on your host machine? Ubuntu was updated to 22 in the container for 1.8.0. Try updating your Docker installation, see if it helps. |
Experiencing the same issue with same debug output. Completely removed and reinstalled docker as per: https://docs.docker.com/engine/install/ubuntu/ and issue persists. Also had v1.7.4 working yesterday. Host: Ubuntu 24.04.1 LTS satisfactory-server | System info: |
Having the same issue after the last Satisfactory update. Ubuntu Version: 22.04.4 LTS |
Running up-to-date Ubuntu 24.04.1 LTS Client: Docker Engine - Community
Version: 27.2.0
API version: 1.47
Go version: go1.21.13
Git commit: 3ab4256
Built: Tue Aug 27 14:15:13 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 27.2.0
API version: 1.47 (minimum version 1.24)
Go version: go1.21.13
Git commit: 3ab5c7d
Built: Tue Aug 27 14:15:13 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.21
GitCommit: 472731909fa34bd7bc9c087e4c27943f9835f111
runc:
Version: 1.1.13
GitCommit: v1.1.13-0-g58aa920
docker-init:
Version: 0.19.0
GitCommit: de40ad0 |
Appreciate the feedback everyone. Please do note that v1.7.3 will work in the meantime!! Trying to figure out why upgrading to Ubuntu 22 has affected any of you. We previously theorized that it was due to older hosts; however, your system Docker is actually a higher version than mine even |
Could one/any of you try following some of the advice in this Reddit thread, please? Curious to hear if any of it makes a difference; https://www.reddit.com/r/archlinux/comments/llgo3x/network_errors_with_steam/ @theabian so it seems to be a connection issue, I'm just curious why specifically with Ubuntu 22 on the container. Please try this: Specifically:
|
Worked like a charm. edited the /etc/hosts and the steamcmd worked in v1.8.3 |
Had to head off to work, but if still an issue later on, I'll run through that and post system info. In the meantime I got v1.7.3 working perfectly. |
So glad to hear it @theabian! I'll leave this open for the time being. Very, very interesting, and I'd love to understand why it's uniquely a problem on Ubuntu 22. |
This fixed my issue, thanks! |
Apologies with coming back to this so late, but I had the same issue as @shade703 , my proxmox VM CPU was QEMU. Changing this to host worked perfectly. Odd though, as QEMU worked perfectly fine for v1.7.4. |
@ElDubsNZ yeah, most likely due to us moving drom Ubuntu 18 to Ubuntu 22 in |
Describe the Bug
On any image v1.8.X the steamcmd states being offline and crashes, while v1.7.4 works fine.
Your Runtime Command or Docker Compose File
Debug Output
System Specs:
===== START ISSUE REPORT ===== OS: Linux docker01 6.8.0-44-generic #44-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 13 13:35:26 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux CPU: Intel(R) Xeon(R) CPU X5670 @ 2.93GHz BIOS Intel(R) Xeon(R) CPU X5670 @ 2.93GHz CPU @ 2.9GHz RAM: 31GB/32GB HDD: 144GB/292GB (52% used) ===== END ISSUE REPORT =====
Logs
logs-v1.7.4.txt
logs-v1.8.3.txt
Additional Context
Fatal error from steamcmd:
The text was updated successfully, but these errors were encountered: