[BUG] SteamCMD Error! Failed to set beta '1' when requesting a nonstable version

[karcsesz]

Describe the bug Tried to start a server with the following Compose file:

services:
  7dtdserver:
    image: vinanrra/7dtd-server
    container_name: 7dtdserver
    environment:
      - START_MODE=1 #Change between START MODES
      - VERSION=latest_experimental # Change between 7 days to die versions
      - PUID=1000 # Remember to use same as your user
      - PGID=1000 # Remember to use same as your user
    volumes:
      - ./7days:/home/sdtdserver/.local/share/7DaysToDie/
      - ./LGSM-Config:/home/sdtdserver/lgsm/config-lgsm/sdtdserver
      - ./log:/home/sdtdserver/log/ # Optional - Logs folder
    ports:
      - 26900:26900/tcp # Default game ports
      - 26900:26900/udp # Default game ports
      - 26901:26901/udp # Default game ports
      - 26902:26902/udp # Default game ports
      - 8082:8082/tcp # OPTIONAL - WEBSERVER https://7dtd.illy.bz/wiki/Server%20fixes
    restart: unless-stopped # INFO - NEVER USE WITH START_MODE=4 or START_MODE=0

But installation kept failing with the error mentioned in the title. After investigation, I've found that SteamCMD was called with -beta -beta latest_experimental instead of the expected -beta latest_experimental.

After editing the first_install.sh script to omit the manually added -beta before the specified VERSION and rebuilding the image locally, the installation started properly.

To Reproduce Steps to reproduce the behavior:

1. Launch container with VERSION=latest_experimental specified (I had also tested other beta versions, they were also broken)
2. Wait for SteamCMD to launch and attempt to install
3. See error

Expected behavior The -beta parameter shouldn't be duplicated

Versions:

• Docker Compose version 2.27.1
• Docker image version: latest as of filing this issue.

Docker/Docker-compose Shown above

Thank you! ^^

[f00d4tehg0dz]

I have the same issue here. thanks for the fix suggestion

[vinanrra]

Hi @karcsesz, I will check the issue and upload a fix ASAP, thanks for the ticket

[vinanrra]

Version 0.7.5 have this issue fixed.