Open theabian opened 5 days ago
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 Docker: 27.2.1 Docker Compose: 2.29.2
satisfactory-server | System info: satisfactory-server | OS: Linux satisfactory-server 6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 2 20:41:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux satisfactory-server | CPU: QEMU Virtual CPU version 2.5+ satisfactory-server | RAM: 39GB/42GB satisfactory-server | HDD: 26GB/293GB (10% used) satisfactory-server | satisfactory-server | Current version: satisfactory-server | 1.8.3 satisfactory-server | Current user: satisfactory-server | uid=0(root) gid=0(root) groups=0(root) satisfactory-server | Proposed user: satisfactory-server | uid=1000(?) gid=1000(?) groups=1000(?) satisfactory-server | satisfactory-server | Exiting...
Having the same issue after the last Satisfactory update.
Ubuntu Version: 22.04.4 LTS Docker Version: 24.0.5
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.
Running up-to-date Ubuntu 24.04.1 LTS Docker Compose: v2.29.2 Docker Engine:
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:
ping media.steampowered.com to get its IP then edit /etc/hosts --- add [The IP] client-download.steampowered.com
@shade703 your issue is probably due to your CPU model being QEMU. Go into Proxmox, set your VM CPU as Host, then reboot.
@ElDubsNZ please edit your reply with your system info, please :) CPU, etc. You can grab the template by going to create a new issue (without actually creating a new issue)
@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:
ping media.steampowered.com to get its IP then edit /etc/hosts --- add [The IP] client-download.steampowered.com
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.
@shade703 your issue is probably due to your CPU model being QEMU. Go into Proxmox, set your VM CPU as Host, then reboot.
@ElDubsNZ please edit your reply with your system info, please :) CPU, etc. You can grab the template by going to create a new issue (without actually creating a new issue)
This fixed my issue, thanks!
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:
Logs
logs-v1.7.4.txt logs-v1.8.3.txt
Additional Context
Fatal error from steamcmd: