Skip to content
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

"This server is unclaimed" every time I restart the container #57

Closed
mythmon opened this issue Oct 29, 2021 · 4 comments
Closed

"This server is unclaimed" every time I restart the container #57

mythmon opened this issue Oct 29, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@mythmon
Copy link

mythmon commented Oct 29, 2021

Thanks for maintaining this image!

Describe the Bug
Every time I restart the container (such as with docker-compose restart), the server becomes unclaimed, and I have to create a game again. My save files are available, if I type the right session name I can get back into the same save. It also prompts for a new admin password each time.

Your Runtime Command or Docker Compose File

version: "3"
services:
  satisfactory-server:
    image: wolveix/satisfactory-server:latest
    ports:
      - 7777:7777/udp # game port
      - 15000:15000/udp # beaccon port
      - 15777:15777/udp # server query port
    volumes:
      - satisfactory-data:/config
      # I realize this isn't exactly supported, but it works for me
      - ./saves:/home/steam/.config/Epic/FactoryGame/Saved/SaveGames/server
    restart: unless-stoppedversion: "3"

  # The problem happens with or without this backup service, but including it here for completeness.
  backups:
    image: southclaws/restic-robot
    hostname: fungeon-satisfactory-backups
    depends_on:
      - satisfactory-server
    volumes:
      - ./saves:/data:ro
      - ./backups:/backups:rw
      - ./backups-cleanup.sh:/backups-cleanup.sh:ro
    env_file:
      - ./secrets.env
    environment:
      SCHEDULE: "0 */15 * * *" # every 15 minute
      RESTIC_REPOSITORY: /backups
      RESTIC_ARGS: /data
      PRUNE_RESTIC_RETENTION: >
        --keep-within 48h
        --keep-daily 7
        --keep-weekly 4
        --keep-monthly 12
      POST_COMMAND: /backups-cleanup.sh
      # Set these in secrets.env
      # RESTIC_PASSWORD:

volumes:
  satisfactory-data:

System Specs (please complete the following information):

$ cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=21.04
DISTRIB_CODENAME=hirsute
DISTRIB_DESCRIPTION="Ubuntu 21.04"
NAME="Ubuntu"
VERSION="21.04 (Hirsute Hippo)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 21.04"
VERSION_ID="21.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=hirsute
UBUNTU_CODENAME=hirsute
@wolveix
Copy link
Owner

wolveix commented Oct 29, 2021

Appreciate the kind words!

I fixed this a couple of days ago. No need to comment on your saves directory, though the saves do get copied back on container restart at least :) Glad it's working for you though!

To confirm, when did you last pull the image? Have you verified that this is happening with the latest image?

wolveix added a commit that referenced this issue Oct 30, 2021
- Added DEBUG flag for debugging
- Added PGID and PUID flags for more control over permissions
- Added SKIPUPDATE flag to skip updating the server
- Fixed permissions issue (#44) by dropping to `root`
- Fixed server settings not persisting (#57)
- Split `init.sh` script into `init.sh ` and `run.sh`
@wolveix
Copy link
Owner

wolveix commented Oct 30, 2021

I believe this has been addressed :)

@wolveix wolveix added the bug Something isn't working label Oct 30, 2021
@wolveix wolveix closed this as completed Oct 30, 2021
wolveix added a commit that referenced this issue Oct 30, 2021
@wolveix wolveix reopened this Oct 30, 2021
@wolveix
Copy link
Owner

wolveix commented Oct 30, 2021

Working on this again. The previous fix broke the server.

@mythmon
Copy link
Author

mythmon commented Oct 30, 2021

With the latest image, this problem is fixed and I don't have segfaults. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants