You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on what I see on the entrypoint.sh file there are a couple of problems that I encountered when using my own supplied config and setting DEDICATED_CFG env.
Despite the dedicated server authorization infos (masterserver login+password) entered in my config file, the entrypoint still demands that MASTER_LOGIN and MASTER_PASSWORD envs are set. This can be worked around by supplying dummy values.
Despite using a different config file, the entrypoint still writes the defaults (and the aforementioned masterserver account dummies) to dedicated_cfg.txt, which is not necessary and can even be harmful if UserData volume is shared across multiple containers.
The text was updated successfully, but these errors were encountered:
Based on what I see on the
entrypoint.sh
file there are a couple of problems that I encountered when using my own supplied config and settingDEDICATED_CFG
env.MASTER_LOGIN
andMASTER_PASSWORD
envs are set. This can be worked around by supplying dummy values.dedicated_cfg.txt
, which is not necessary and can even be harmful ifUserData
volume is shared across multiple containers.The text was updated successfully, but these errors were encountered: