ensl / ensl_hlds Goto Github PK

entry.sh has the following line:

./hlds_run $HLDS_OPTS

.env (or .env.default) contain the following:

HLDS_OPTS=-game ns +maxplayers 32 +log on +map ns_veil +exec ns/server.cfg -port 27016 -pingboost 3 +sys_ticrate 1000

which results in:

Console initialized.
WARNING: W_LoadWadFile, couldn't load fonts.wad
FATAL ERROR (shutting down): Couldn't find 'decals.wad' in "DEFAULTGAME" search path

these fatal errors are written to a file called debug.log on the container by default, so I added the following line to write and persist them the logs folder during diagnostics

./hlds_run $HLDS_OPTS >> /home/steam/hlds/ns/logs/debug.log &

I then tried specifying ./hlds_linux $HLDS_OPTS specifically here, but has the same result.

I tried the [hlds_linux] New feature: -insert_search_path switch (for both hlds_linux and hlds_run -- it does not resolve the issue (or seem to function even).

with clean pull of this repository (and no images/containers preexisting)

ran docker-compose up --build and received the following error:

failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to parse stage name "HLDS_NS": invalid reference format: repository name must be lowercase

I don't know why this wasn't a build error in my environment during February 2020 -- when I last worked on docker composer and DockerFile changes - but uppercase repository naming is invalid format, even for staging.

reference material: stackoverflowcom - docker-error-invalid-reference-format-repository-name-must-be-lowercase

docker-compose fails with error message Unable to locate package libcurl3:i386. I believe this is because this package does not exist in Ubuntu 20.

this actually relates to another error I saw this morning, which was DEFAULTGAME search path ID not finding decals.wad. This fatally crashes hlds from starting -- I may end up creating a separate issue for it specifically, since SteamPipe is a separate matter from this: base images for containers.

when reviewing on GoldSrc SteamPipe directories documentation (https://developer.valvesoftware.com/wiki/GoldSrc_SteamPipe_Directories)

there was a wiki link referencing to using steamcmd for container development: https://github.com/CM2Walki/steamcmd

Add variables for variable information (eg. build information) and make the docker plugin be completely independent from plugin / game release.

Add some sort of test automation. Use Dockerfile.

• Use either Travis or Circle CI to install HLDS, start the server, load AMXX plugins and test it works.
• Do the same but with several operating systems. Eg. ubuntu, fedora, debian, centos, opensuse.
• Just start the server and make sure it responds to RCON request, as HLDS client request is hard to simulate.

Use env subst.