irobot73 commented 2 years ago

Describe the bug Get a WARN, when starting the server, that the system is missing a dependency.

To Reproduce Steps to reproduce the behavior:

Pull
Setup
Start up Docker instance
Warning in log noted directly after 'Starting server...'

Expected behavior No Warning to exist (@ least it's not an ERROR)

Screenshots Screenshot of warning

Versions:

3
vinanrra/7dtd-server

Docker/Docker-compose

version: "3" services: 7dtdserver: image: vinanrra/7dtd-server # https://github.com/vinanrra/Docker-7DaysToDie container_name: 7dtdserver environment:

ALLOC_FIXES=NO # Optional - Install Allocs Fixes
ALLOC_FIXES_UPDATE=NO # Optional - Update Allocs Fixes, depending of your 7 days to die version, on server install
BACKUP=YES # Optional - Backup server at 5 AM
MONITOR=YES # Optional - Keeps server up if crash
PUID=1000
PGID=1000

START_MODE=3 # REQUIRED - Change between START MODES #

Start Modes

                                #
                                # 0 Install server
                                # 1 Start server
                                # 2 Update server
                                # 3 Update server and start, useful if you have already a 7 Days To Die server installed
                                # 4 Backup server and STOP the container
                                #

TEST_ALERT=YES # Test alerts at start of server
TimeZone=America/New_York
VERSION=stable # Change between 7 days to die versions
'stable' or 'latest_experimental' or...
```
                                #    https://steamdb.info/app/251570/depots/
```
volumes:
/nas/Data/steam/[Games]/7days2die/svr:/home/sdtdserver/serverfiles/ # 7DaysToDie server config files.
/nas/Data/steam/[Games]/7days2die/userData:/home/sdtdserver/.local/share/7DaysToDie/ # 7DaysToDie saves, where maps are store.
/nas/Data/steam/LGSM/Logs:/home/sdtdserver/log/ # 7DaysToDie server log files.
/nas/Data/steam/LGSM/Backup:/home/sdtdserver/lgsm/backup/ # 7DaysToDie server backups files.
/nas/Data/steam/LGSM/Config:/home/sdtdserver/lgsm/config-lgsm/sdtdserver/ # LGSM config files.
/nas:/media ports:
80:80/tcp # EAC/EOS (testing)
443:443/tcp # EAC/EOS (testing)
26900:26900/tcp # PC
26900-26905:26900-26905/udp # PC (added few 'extra' ports to CYA)
27015-27050:27015-27050/udp # Valve (server registration)
[added more ports via https://7dtd.illy.bz/wiki/Ports]
1935:1935/tcp # Playstation
3478-3480:3478-3480/udp # Playstation
3074:3074/tcp # X-Box
3074:3076:3074:3076/udp # X-Box
(all the above via https://portforward.com/7-days-to-die/)
8083:8083/tcp # OPTIONAL WEBADMIN [NOTE: match server's CFG file]
8084:8084/tcp # OPTIONAL TELNET [NOTE: match server's CFG file]
8085:8085/tcp # OPTIONAL WEBSERVER https://7dtd.illy.bz/wiki/Server%20fixes

8087:8087/tcp # OPTIONAL WEBSERVER https://github.com/dmustanger/7dtd-ServerTools restart: unless-stopped # NEVER USE WITH START_MODE=0, 2 or 4

"no"

                            #    always
                            #    on-failure
                            #    unless-stopped
                            # 
                            # https://developer.valvesoftware.com/wiki/SteamCMD

Additional context Add any other context about the problem here.

vinanrra commented 2 years ago

Pushed a new release that fix that, could you test it?

irobot73 commented 2 years ago

Sorry, no love (pruned all images/containers prior to latest server run):

7dtdserver    |         https://github.com/vinanrra/Docker-7DaysToDie/blob/master/README.md
7dtdserver    |         =======================================================================
7dtdserver    | 
7dtdserver    |  * Starting periodic command scheduler cron
7dtdserver    |    ...done.
7dtdserver    | [INFO] Activated automatic backup at 5AM
7dtdserver    | [INFO] Activated LinuxGSM server monitoring
[ FAIL ] Updating sdtdserver: Checking remote build: SteamCMD[INFO] The server have been updated to stable
7dtdserver    | [INFO] Installing mods after first start
7dtdserver    | [INFO] The server mods have been updated to latest version, if the server crash, check mod compatibilites
7dtdserver    | [INFO] Starting server...
[ WARN ] Starting sdtdserver: Missing dependencies: distro-infosudo dpkg --add-architecture i386; sudo apt update; sudo apt install distro-info
[  OK  ] Starting sdtdserver: Applying steamclient.so sdk64 hardlink fix: 7 Days To Die
[  OK  ] Starting sdtdserver: Applying steamclient.so sdk32 link fix: 7 Days To Die

I didn't note any addition(s) to the DockerFile depend??

vinanrra commented 2 years ago

It was an update of the LinuxGsm script, the image pull the new version when the image it's created, and I just notice that it's missing an package apart of the update of the script.

Ancitik commented 2 years ago

Hi @vinanrra , thank you for your work.

Just pulled the v0.3.2 (latest) and recreated the container (updating from 20.4 to 20.5) but still have this message.

[ FAIL ] Updating sdtdserver: Checking remote build: SteamCMD[INFO] The server have been updated to stable
[ ... ]
[ WARN ] Starting sdtdserver: Missing dependencies: distro-infosudo dpkg --add-architecture i386; sudo apt update; sudo apt install distro-info

I tried to manually apt install distro-info in the container, the package manager found something to install so maybe the image is not up to date.

vinanrra commented 2 years ago

Hi @vinanrra , thank you for your work.

Just pulled the v0.3.2 (latest) and recreated the container (updating from 20.4 to 20.5) but still have this message.
[ FAIL ] Updating sdtdserver: Checking remote build: SteamCMD[INFO] The server have been updated to stable
[ ... ]
[ WARN ] Starting sdtdserver: Missing dependencies: distro-infosudo dpkg --add-architecture i386; sudo apt update; sudo apt install distro-info
I tried to manually apt install distro-info in the container, the package manager found something to install so maybe the image is not up to date.

Do an apt update first and try again

Ancitik commented 2 years ago

I did it and i found the package. To fix this we just have to had the package name line 47 of the Dockerfile.

I did it locally and built the image. My server don't have this warning anymore while running on the fixed docker image. I still have the issue https://github.com/vinanrra/Docker-7DaysToDie/issues/115

vinanrra commented 2 years ago

Fixed #113

irobot73 commented 2 years ago

Fixed #113

Seems so. No WARN noted after a pull of the new code. TY

[INFO] Installing mods after first start
[INFO] The server mods have been updated to latest version, if the server crash, check mod compatibilites
[INFO] Starting server...
fetching GitHub command_start.sh...OK
fetching GitHub check_executable.sh...OK
fetching GitHub check_glibc.sh...OK
fetching GitHub info_distro.sh...OK
fetching GitHub check_deps.sh...OK
checking GitHub ubuntu-18.04.csv...OK
fetching GitHub ubuntu-18.04.csv...OK
fetching GitHub check_config.sh...OK
fetching GitHub check_system_requirements.sh...OK
fetching GitHub fix.sh...OK
fetching GitHub fix_steamcmd.sh...OK

[ .... ] Starting sdtdserver: Applying steamclient.so sdk64 hardlink fix: 7 Days To Die
[ INFO ] Starting sdtdserver: Applying steamclient.so sdk64 hardlink fix: 7 Days To Die
[  OK  ] Starting sdtdserver: Applying steamclient.so sdk64 hardlink fix: 7 Days To Die

[ .... ] Starting sdtdserver: Applying steamclient.so sdk32 link fix: 7 Days To Die
[ INFO ] Starting sdtdserver: Applying steamclient.so sdk32 link fix: 7 Days To Die
[  OK  ] Starting sdtdserver: Applying steamclient.so sdk32 link fix: 7 Days To Die
fetching GitHub fix_sdtd.sh...OK

[ .... ] Starting sdtdserver: Double-D's 7D2D Server
[  OK  ] Starting sdtdserver: Double-D's 7D2D Server

vinanrra / Docker-7DaysToDie

[BUG] Missing 'distro-info' dependancy #113

Docker/Docker-compose

Start Modes

'stable' or 'latest_experimental' or...

[added more ports via https://7dtd.illy.bz/wiki/Ports]

(all the above via https://portforward.com/7-days-to-die/)

"no"