satisfactory-server: ln: failed to create symbolic link '/home/steam/.steam/steam': No such file or directory
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
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 43 (22 by maintainers)
Commits related to this issue
- Rebased back to Ubuntu 18 (#186) — committed to wolveix/satisfactory-server by wolveix a 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 😃
@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. 😃
Yes, seems to be working just fine
Works just fine! Thanks for your quick response and great effort!
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!
Yeah, but
v1.4.9
won’t work with theexperimental
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