wolveix / satisfactory-server

A Dockerized version of the Satisfactory dedicated server
https://hub.docker.com/r/wolveix/satisfactory-server
MIT License
1.05k stars 128 forks source link

ln: failed to create symbolic link '/home/steam/.steam/steam': No such file or directory #186

Closed wasnertobias closed 1 year ago

wasnertobias commented 1 year ago

I have just updated to the latest docker image using

sudo docker-compose pull
sudo docker-compose up -d

However after startup I ran into the following issue as seen in the logs.

Logs

sudo docker-compose logs
WARNING: Some services (satisfactory-server) use the 'deploy' key, which will be ignored. Compose does not support 'deploy' configuration - use `docker stack deploy` to deploy to a swarm.
Attaching to satisfactory-server
satisfactory-server    | Checking available memory...20GB detected
satisfactory-server    | Setting autosave number to 5
satisfactory-server    | Setting crash reporting to True
satisfactory-server    | Setting max objects number to 2162688
satisfactory-server    | Setting max tick rate to 120
satisfactory-server    | Setting timeout number to 300
satisfactory-server    | Setting max players to 4
satisfactory-server    | Setting autosave interval to 300s
satisfactory-server    | Setting disable seasonal events to 0
satisfactory-server    | Setting network quality number to 3
satisfactory-server    | Setting auto pause to True
satisfactory-server    | Setting autosave on disconnect to True
satisfactory-server    | Experimental flag is set. Experimental will be downloaded instead of Early Access.
satisfactory-server    | Checking available storage...190GB detected
satisfactory-server    | Downloading the latest version of the game...
satisfactory-server    | ln: failed to create symbolic link '/home/steam/.steam/root': No such file or directory
satisfactory-server    | ln: failed to create symbolic link '/home/steam/.steam/steam': No such file or directory

My docker-compose.yml in /home/xxx/satisfactory:

version: '3'
services:
    satisfactory-server:
        container_name: 'satisfactory-server'
        hostname: 'satisfactory-server'
        image: 'wolveix/satisfactory-server:latest'
        ports:
            - '7777:7777/udp'
            - '15000:15000/udp'
            - '15777:15777/udp'
        volumes:
            - '/home/xxx/satisfactory/config:/config'
        environment:
            - MAXPLAYERS=4
            - PGID=1000
            - PUID=1000
            - STEAMBETA=true
        restart: unless-stopped
        deploy:
          resources:
            limits:
              memory: 16G
            reservations:
              memory: 12G
wolveix commented 1 year ago

Hey!

Those are normal issues, the server should still startup fine? Is the server not starting up for you?

wasnertobias commented 1 year ago

Hey, thank you for your reply. Well, nothing else is being logged afterwards, no network activity is happening on the host machine - gameserver is not reachable. So I assumed it will have to do sth with those latest log msgs.

wolveix commented 1 year ago

Ah I see, I'm sorry to hear that! Let me see if I can reproduce this issue with a clean environment. In the meantime, would you mind providing your system information? Please check the issue template for the format :)

wasnertobias commented 1 year ago

Sure thing, sorry that I missed that before!

===== START ISSUE REPORT =====
OS:  Linux onix 4.9.0-14-amd64 #1 SMP Debian 4.9.240-2 (2020-10-30) x86_64 GNU/Linux
CPU: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
RAM: 20GB/32GB
HDD: 773GB/1GB (77% used)
===== END ISSUE REPORT =====

(side note: Guess that should be 1 TB not GB total storage)

wolveix commented 1 year ago

Hm, yeah this is strange. I can't reproduce this at all. Could you see if the issues persists without the volume mount? Also, make sure you're using the latest version of the image (docker compose pull)

wasnertobias commented 1 year ago

Hey, I get exactly the same behaviour without the volume mount. Also I made sure to run docker-compose pull once again.

wolveix commented 1 year ago

@wasnertobias could you post the output of docker images | grep wolveix/satisfactory?

wasnertobias commented 1 year ago
wolveix/satisfactory-server           latest              8e8bf96efa02        4 days ago          431MB
wolveix/satisfactory-server           <none>              2424989405f0        3 months ago        412MB
wolveix/satisfactory-server           <none>              f6a18906a180        4 months ago        411MB
wolveix commented 1 year ago

Thanks :) Could you try running the image with STEAMBETA=false?

wasnertobias commented 1 year ago

Sure! I cannot see any different output with STEAMBETA=false. Anything more I could try to debug?

wolveix commented 1 year ago

Hm, this is strange! It seems like it's getting hung up when calling Steam. How long have you left it for? Have you left it for at least 10 minutes?

Try executing into the container and running steamcmd manually:

docker exec -it satisfactory-server /bin/bash
steamcmd +force_install_dir /config/gamefiles +login anonymous +app_update 1690800 -beta experimental validate +quit
wasnertobias commented 1 year ago

We are getting a lot closer here...

root@satisfactory-server:/config# steamcmd +force_install_dir /config/gamefiles +login anonymous +app_update 1690800 -beta experimental validate +quit Redirecting stderr to '/root/Steam/logs/stderr.txt' Looks like steam didn't shutdown cleanly, scheduling immediate update check src/tier0/threadtools.cpp (3760) : Assertion Failed: Failed to create thread (error 0x1)

and

root@satisfactory-server:/config# cat /root/Steam/logs/stderr.txt Installing breakpad exception handler for appid(steam)/version(1685487853)/tid(84) src/tier0/threadtools.cpp (3760) : Assertion Failed: Failed to create thread (error 0x1) assert_20230614123828_4.dmp[87]: Uploading dump (out-of-process) /tmp/dumps/assert_20230614123828_4.dmp assert_20230614123828_4.dmp[87]: Finished uploading minidump (out-of-process): success = no assert_20230614123828_4.dmp[87]: error: libcurl.so: cannot open shared object file: No such file or directory assert_20230614123828_4.dmp[87]: file ''/tmp/dumps/assert_20230614123828_4.dmp'', upload no: ''libcurl.so: cannot open shared object file: No such file or directory''

wolveix commented 1 year ago

Hah, interesting. Try running apt-get update && apt-get install libcurl3 -y

wasnertobias commented 1 year ago

Inside the docker container i suppose?

root@satisfactory-server:/config# apt-get update && apt-get install libcurl3 -y
Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:2 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Err:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Err:2 http://archive.ubuntu.com/ubuntu jammy InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [108 kB]
Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Reading package lists... Done
W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://security.ubuntu.com/ubuntu jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
E: Sub-process returned an error code
wolveix commented 1 year ago

Scratch that. Start a clean container, leave it for a couple of minutes, and post the output of this:

docker exec -it satisfactory-server cat /root/Steam/logs/stderr.txt
wasnertobias commented 1 year ago

So I have now stopped and removed the existing one, spun it up again - no different log output & no network activity.

xxx@onix:~/satisfactory$ sudo docker exec -it satisfactory-server cat /root/Steam/logs/stderr.txt
Installing breakpad exception handler for appid(steam)/version(1685487853)/tid(43)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(44)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(45)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(46)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(47)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(48)
CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(49)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(50)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(51)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(52)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(53)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(54)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(55)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(56)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(57)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(58)
Installing breakpad exception handler for appid(steamcmd)/version(1685487853)/tid(59)

Will wait a few more minutes and tell you if something else happens.

Bethibande commented 1 year ago

@wasnertobias, have you found a way to resolve this yet? I'm having the same issue.

wolveix commented 1 year ago

@Bethibande could you share you system info and Docker Compose (or run command), please? See the issue template for more information.

I'm hoping to see something similar in your two setups

wasnertobias commented 1 year ago

I have just downgraded to version v1.4.9 and it is now successfully downloading the update. So #184 seems to be the issue root cause for me:

Attaching to satisfactory-server
satisfactory-server    | Checking available memory...20GB detected
satisfactory-server    | Setting autosave number to 5
satisfactory-server    | Setting crash reporting to True
satisfactory-server    | Setting max objects number to 2162688
satisfactory-server    | Setting max tick rate to 120
satisfactory-server    | Setting timeout number to 300
satisfactory-server    | Setting max players to 4
satisfactory-server    | Setting autosave interval to 300s
satisfactory-server    | Setting disable seasonal events to 0
satisfactory-server    | Setting network quality number to 3
satisfactory-server    | Setting auto pause to True
satisfactory-server    | Setting autosave on disconnect to True
satisfactory-server    | Experimental flag is set. Experimental will be downloaded instead of Early Access.
satisfactory-server    | Checking available storage...190GB detected
satisfactory-server    | Downloading the latest version of the game...
satisfactory-server    | Redirecting stderr to '/home/steam/.steam/logs/stderr.txt'
satisfactory-server    | ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt".
satisfactory-server    | [  0%] Checking for available update...
satisfactory-server    | [  0%] Downloading update (0 of 87,267 KB)...
satisfactory-server    | [  0%] Downloading update (4,343 of 87,267 KB)...
satisfactory-server    | [  4%] Downloading update (9,445 of 87,267 KB)...
satisfactory-server    | [ 10%] Downloading update (14,857 of 87,267 KB)...
satisfactory-server    | [ 17%] Downloading update (18,672 of 87,267 KB)...
satisfactory-server    | [ 21%] Downloading update (23,238 of 87,267 KB)...
satisfactory-server    | [ 26%] Downloading update (27,409 of 87,267 KB)...
satisfactory-server    | [ 31%] Downloading update (31,574 of 87,267 KB)...
satisfactory-server    | [ 36%] Downloading update (35,759 of 87,267 KB)...
satisfactory-server    | [ 40%] Downloading update (40,339 of 87,267 KB)...
satisfactory-server    | [ 46%] Downloading update (44,505 of 87,267 KB)...
satisfactory-server    | [ 50%] Downloading update (48,602 of 87,267 KB)...
satisfactory-server    | [ 55%] Downloading update (53,191 of 87,267 KB)...
satisfactory-server    | [ 60%] Downloading update (57,378 of 87,267 KB)...
satisfactory-server    | [ 65%] Downloading update (59,713 of 87,267 KB)...
satisfactory-server    | [ 68%] Downloading update (62,007 of 87,267 KB)...
satisfactory-server    | [ 71%] Downloading update (63,227 of 87,267 KB)...
satisfactory-server    | [ 72%] Downloading update (65,310 of 87,267 KB)...
satisfactory-server    | [ 74%] Downloading update (67,611 of 87,267 KB)...
satisfactory-server    | [ 77%] Downloading update (69,696 of 87,267 KB)...
satisfactory-server    | [ 79%] Downloading update (71,782 of 87,267 KB)...
satisfactory-server    | [ 82%] Downloading update (73,861 of 87,267 KB)...
satisfactory-server    | [ 84%] Downloading update (76,186 of 87,267 KB)...
satisfactory-server    | [ 87%] Downloading update (78,219 of 87,267 KB)...
satisfactory-server    | [ 89%] Downloading update (79,977 of 87,267 KB)...
satisfactory-server    | [ 91%] Downloading update (82,276 of 87,267 KB)...
satisfactory-server    | [ 94%] Downloading update (84,361 of 87,267 KB)...
satisfactory-server    | [ 96%] Downloading update (86,444 of 87,267 KB)...
satisfactory-server    | [ 99%] Downloading update (87,267 of 87,267 KB)...
satisfactory-server    | [100%] Download Complete.
satisfactory-server    | [----] Applying update...
satisfactory-server    | [----] Extracting package...
satisfactory-server    | [----] Extracting package...
satisfactory-server    | [----] Extracting package...
satisfactory-server    | [----] Extracting package...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Cleaning up...
satisfactory-server    | [----] Update complete, launching...
satisfactory-server    | Redirecting stderr to '/home/steam/.steam/logs/stderr.txt'
satisfactory-server    | /tmp/dumps is not owned by us - delete and recreate
satisfactory-server    | Unable to delete /tmp/dumps. Continuing anyway.
satisfactory-server    | [  0%] Checking for available updates...
satisfactory-server    | [----] Downloading update (60 of 57,697 KB)...
satisfactory-server    | [  0%] Downloading update (3,338 of 57,697 KB)...
satisfactory-server    | [  5%] Downloading update (7,302 of 57,697 KB)...
satisfactory-server    | [ 12%] Downloading update (9,751 of 57,697 KB)...
satisfactory-server    | [ 16%] Downloading update (12,460 of 57,697 KB)...
satisfactory-server    | [ 21%] Downloading update (14,923 of 57,697 KB)...
satisfactory-server    | [ 25%] Downloading update (17,158 of 57,697 KB)...
satisfactory-server    | [ 29%] Downloading update (19,610 of 57,697 KB)...
satisfactory-server    | [ 33%] Downloading update (22,309 of 57,697 KB)...
satisfactory-server    | [ 38%] Downloading update (24,768 of 57,697 KB)...
satisfactory-server    | [ 42%] Downloading update (27,229 of 57,697 KB)...
satisfactory-server    | [ 47%] Downloading update (29,925 of 57,697 KB)...
satisfactory-server    | [ 51%] Downloading update (31,939 of 57,697 KB)...
satisfactory-server    | [ 55%] Downloading update (34,376 of 57,697 KB)...
satisfactory-server    | [ 59%] Downloading update (37,067 of 57,697 KB)...
satisfactory-server    | [ 64%] Downloading update (39,464 of 57,697 KB)...
satisfactory-server    | [ 68%] Downloading update (41,080 of 57,697 KB)...
satisfactory-server    | [ 71%] Downloading update (42,675 of 57,697 KB)...
satisfactory-server    | [ 73%] Downloading update (44,027 of 57,697 KB)...
satisfactory-server    | [ 76%] Downloading update (45,254 of 57,697 KB)...
satisfactory-server    | [ 78%] Downloading update (46,487 of 57,697 KB)...
satisfactory-server    | [ 80%] Downloading update (47,838 of 57,697 KB)...
satisfactory-server    | [ 82%] Downloading update (49,066 of 57,697 KB)...
satisfactory-server    | [ 85%] Downloading update (50,293 of 57,697 KB)...
satisfactory-server    | [ 87%] Downloading update (51,650 of 57,697 KB)...
satisfactory-server    | [ 89%] Downloading update (52,881 of 57,697 KB)...
satisfactory-server    | [ 91%] Downloading update (54,105 of 57,697 KB)...
satisfactory-server    | [ 93%] Downloading update (55,455 of 57,697 KB)...
satisfactory-server    | [ 96%] Downloading update (56,682 of 57,697 KB)...
satisfactory-server    | [ 98%] Downloading update (57,697 of 57,697 KB)...
satisfactory-server    | [100%] Download complete.
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Extracting package...
satisfactory-server    | [----] Extracting package...
satisfactory-server    | [----] Extracting package...
satisfactory-server    | [----] Extracting package...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Installing update...
satisfactory-server    | [----] Cleaning up...
satisfactory-server    | [----] Update complete, launching Steamcmd...
satisfactory-server    | Redirecting stderr to '/home/steam/.steam/logs/stderr.txt'
satisfactory-server    | /tmp/dumps is not owned by us - delete and recreate
satisfactory-server    | Unable to delete /tmp/dumps. Continuing anyway.
satisfactory-server    | [  0%] Checking for available updates...
satisfactory-server    | [----] Verifying installation...
satisfactory-server    | Steam Console Client (c) Valve Corporation - version 1685487853
satisfactory-server    | -- type 'quit' to exit --
satisfactory-server    | Loading Steam API...OK
satisfactory-server    |
satisfactory-server    | Connecting anonymously to Steam Public...OK
satisfactory-server    | Waiting for client config...OK

BTW: The docker version on my machine is pretty old - though I am unable to update easily due to other dependencies:

Client: Docker Engine - Community
 Version:           19.03.15
 API version:       1.40
 Go version:        go1.13.15
 Git commit:        99e3ed8919
 Built:             Sat Jan 30 03:17:11 2021
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.15
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       99e3ed8919
  Built:            Sat Jan 30 03:15:40 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.3
  GitCommit:        269548fa27e0089a8b8278fc4fc781d7f65a939b
 runc:
  Version:          1.0.0-rc92
  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683
wolveix commented 1 year ago

Yeah, but v1.4.9 won't work with the experimental branch. It'll download, but it'll fail to launch due to the most recent major update. I wonder if the rebase to Ubuntu 22 causes the issue somehow. I'll make a build without that change and I'll push it for you to try

wasnertobias commented 1 year ago

That's what I expected @wolveix - if I got the time later I will build the docker image myself with the correct launch scripts for experimental but without the Ubuntu 22 rebase.

wolveix commented 1 year ago

@wasnertobias try switching your image tag from latest to 186. Let me know if that works!

wasnertobias commented 1 year ago

Yes, seems to work according to the startup logs! Will try to launch an actual session now, one sec.. Yep, joining the server etc. works just fine!

wolveix commented 1 year ago

Excellent news! I rebased that tag to Ubuntu 18, I've just rebased it to Ubuntu 20. Would you mind giving that a try too? If that works, then we can keep it there

wasnertobias commented 1 year ago

Tag 186, right? Will try that one as well now!

wolveix commented 1 year ago

Yep, tag 186. Thank you!

Bethibande commented 1 year ago

Tag 186 isn't starting on my system, the download is stuck at 21,211 of 57,746 KB :I

wolveix commented 1 year ago

You might've downloaded it while I was pushing a new version. Stop the download, start it again. Docker hangs sometimes with image downloads

Bethibande commented 1 year ago

I meant the steam download, "docker logs satisfactory-server" just spams "[ 36%] Downloading update (21,211 of 75,746 KB)..."

wolveix commented 1 year ago

Ah, that's still a client-side issue. Try stopping and removing the container, then starting it again

wasnertobias commented 1 year ago

186 seems to be stuck in a restart-loop:

satisfactory-server    | Checking available storage...191GB detected
satisfactory-server    | Downloading the latest version of the game...
satisfactory-server    | Checking available memory...20GB detected
satisfactory-server    | Setting autosave number to 5
satisfactory-server    | Setting crash reporting to True
satisfactory-server    | Setting max objects number to 2162688
satisfactory-server    | Setting max tick rate to 120
satisfactory-server    | Setting timeout number to 300
satisfactory-server    | Setting max players to 4
satisfactory-server    | Setting autosave interval to 300s
satisfactory-server    | Setting disable seasonal events to 0
satisfactory-server    | Setting network quality number to 3
satisfactory-server    | Setting auto pause to True
satisfactory-server    | Setting autosave on disconnect to True
satisfactory-server    | Experimental flag is set. Experimental will be downloaded instead of Early Access.
satisfactory-server    | Checking available storage...191GB detected
satisfactory-server    | Downloading the latest version of the game...
satisfactory-server    | Checking available memory...20GB detected
satisfactory-server    | Setting autosave number to 5
satisfactory-server    | Setting crash reporting to True
satisfactory-server    | Setting max objects number to 2162688
satisfactory-server    | Setting max tick rate to 120
satisfactory-server    | Setting timeout number to 300
satisfactory-server    | Setting max players to 4
satisfactory-server    | Setting autosave interval to 300s
satisfactory-server    | Setting disable seasonal events to 0
satisfactory-server    | Setting network quality number to 3
satisfactory-server    | Setting auto pause to True
satisfactory-server    | Setting autosave on disconnect to True
satisfactory-server    | Experimental flag is set. Experimental will be downloaded instead of Early Access.
satisfactory-server    | Checking available storage...191GB detected
satisfactory-server    | Downloading the latest version of the game...
satisfactory-server    | Checking available memory...20GB detected
satisfactory-server    | Setting autosave number to 5
satisfactory-server    | Setting crash reporting to True
satisfactory-server    | Setting max objects number to 2162688
satisfactory-server    | Setting max tick rate to 120
satisfactory-server    | Setting timeout number to 300
satisfactory-server    | Setting max players to 4
satisfactory-server    | Setting autosave interval to 300s
satisfactory-server    | Setting disable seasonal events to 0
satisfactory-server    | Setting network quality number to 3
satisfactory-server    | Setting auto pause to True
satisfactory-server    | Setting autosave on disconnect to True
satisfactory-server    | Experimental flag is set. Experimental will be downloaded instead of Early Access.
satisfactory-server    | Checking available storage...191GB detected
satisfactory-server    | Downloading the latest version of the game...
satisfactory-server    | Checking available memory...20GB detected
satisfactory-server    | Setting autosave number to 5
satisfactory-server    | Setting crash reporting to True
satisfactory-server    | Setting max objects number to 2162688
satisfactory-server    | Setting max tick rate to 120
satisfactory-server    | Setting timeout number to 300
satisfactory-server    | Setting max players to 4
satisfactory-server    | Setting autosave interval to 300s
satisfactory-server    | Setting disable seasonal events to 0
satisfactory-server    | Setting network quality number to 3
satisfactory-server    | Setting auto pause to True
satisfactory-server    | Setting autosave on disconnect to True
satisfactory-server    | Experimental flag is set. Experimental will be downloaded instead of Early Access.
satisfactory-server    | Checking available storage...191GB detected
satisfactory-server    | Downloading the latest version of the game...

900c6444a43d wolveix/satisfactory-server:186 "/init.sh" 3 minutes ago Restarting (1) About a minute ago satisfactory-server

wolveix commented 1 year ago

Hah, so Ubuntu 20 doesn't work either. Interesting

Bethibande commented 1 year ago

Deleted and recreated the container, this time it's not even downloading its stuck at

Checking available memory...48GB detected
Setting autosave number to 5
Setting crash reporting to True
Setting max objects number to 2162688
Setting max tick rate to 120
Setting timeout number to 300
Setting max players to 3
Setting autosave interval to 300s
Setting disable seasonal events to 0
Setting network quality number to 3
Setting auto pause to True
Setting autosave on disconnect to True
Experimental flag is set. Experimental will be downloaded instead of Early Access.
Checking available storage...1418GB detected
Downloading the latest version of the game...
wolveix commented 1 year ago

@Bethibande yeah, because it's Ubuntu 20. Same as @wasnertobias

wolveix commented 1 year ago

I've rebased the repo back to Ubuntu 18, reversing @Stealthii's recent PR (#184). The latest image should be updated momentarily

wolveix commented 1 year ago

@wasnertobias @Bethibande please try pulling latest, this image should now function as expected for you two.

@Stealthii perhaps we could add a build step for future images to include a Ubuntu 22 variant to address those IPv6 issues you were experiencing? I must confess, I haven't experienced any IPv6 issues myself using the Ubuntu 18 build, so I'd love to explore that further with your input :)

wasnertobias commented 1 year ago

Works just fine! Thanks for your quick response and great effort!

wolveix commented 1 year ago

Thanks for your assistance with all of the trial and error :D Glad we got it figured out :)

Bethibande commented 1 year ago

Yes, seems to be working just fine

csreynolds commented 1 year ago

Pretty sure the problem is the older version of docker installed on @wasnertobias's host.

I'm running the ubuntu:22 version from this morning just fine on experimental but I am running latest docker engine.

[creynolds@localhost ~]$ docker info
Client: Docker Engine - Community
 Version:    24.0.2
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.10.5
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.18.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose
  scan: Docker Scan (Docker Inc.)
    Version:  v0.23.0
    Path:     /usr/libexec/docker/cli-plugins/docker-scan

A websearch will show results that newer ubuntu containers just plain don't apt-anything with older versions of docker engine. example1: https://stackoverflow.com/questions/72624687/apt-get-update-fails-on-ubuntu-22-base-docker-image

wolveix commented 1 year ago

@csreynolds yeah, it worked fine for the majority of users as far as I could tell (myself included). But there's no harm in rebasing back to Ubuntu 18 for the time being as it resolves the issue for the number of users that were impacted. Steamcmd (the upstream image) still actively maintains their Ubuntu 18 image too, if they didn't, I'd stick to the Ubuntu 22 image

csreynolds commented 1 year ago

@wolveix No worries, didn't think the 22 update bought anything other than the listed compatibility problems.

Just adding context in the thread if it comes up again. :)

wolveix commented 1 year ago

@csreynolds I appreciate the additional context :D It'll surely save time when we consider rebasing in the future