search

Thalhalla / thalhalla-catalog

Thalhalla catalog with lots of gaming related
GNU General Public License v3.0
0 stars 1 forks source link

Suggestions/observations running Arma images #2

Open wallopthecat opened 7 years ago

wallopthecat commented 7 years ago

Suggestions/learnings

  1. for storage driver, I used rancher-nfs, convoy-nfs is deprecated in stable docker afaik - although this is a specific implementation detail I thought it worth noting
  2. add instructions to add catalog to rancher in Readme.md for noobs like me 
    - In your rancher go into `/admin/settings`
- then click the `add catalog` button
- then add a Thalhalla catalog https://github.com/Thalhalla/thalhalla-catalog on the `master` branch
- Finally click Save and check out your new catalog.

    Errors/Issues

  3. ~Arma3-Cluster -- all HCs fail with exec: "/assets/headless.sh": stat /assets/headless.sh: no such file or directory I assume this should be pointed to /assets/baked-headless.sh instead (based on what I see in Arma3-Cluster-PW)~
  4. ~maxPlayers is reset to maxPlayers = ""; when stopping/starting Arma3-Cluster-PW~ added the MAX_PLAYERS var to fix
  5. Is it possible to remove the hostname param and instead useserver config file to set server name?
  6. password not set in server config (password is not in default config) for cluster-pw, so headless clients do not connect (they try to connect with pass, but server does not have password)
joshuacox commented 7 years ago

suggestions:

  1. done, thanks for the suggestion, convoy-nfs is deprecated
  2. done, again, thanks

errors:

  1. the different startup scripts is totally confusing and will be replaced by a unified script with options
  2. MAX_PLAYERS should be defaulting to 64, let me know if you get anymore funny business there
  3. in theory, yes, you should be able to set it there, though I might need to add this situation to the unified script above with an option
  4. cluster-pw is most likely borked from not being kept up, but I just updated it to 0.3.6, testing it now
wallopthecat commented 7 years ago

Right on, thanks for the quick responses/action! Some more notes (I'll edit as I learn):

  1. Docker base image could cache Arma install. Add volumes for mods, mpmissions, keys, server config files, and params to pass to ./arma3server - example image here - saves bandwidth and moves configuration to runtime rather than buildtime. in addition, multiple images can share same mod folders etc
  2. New to headless clients, but I was under the assumption they had to load the same modset as server? Current HCs in cluster connect with empty modset
  3. Mods listed in this format fail (only the first mod is loaded): @cba_a3;@ace;@overthrow;@werthless; - they need to be escaped for lgsm apparently: @cba_a3\;@ace\;@overthrow\;@werthless\;
  4. 0.3.6 has the server segfaulting, I assume because of the steam_client.so bug?
wallopthecat commented 7 years ago

Do you have a discord or another way to go back and forth on some of this stuff, or is this the best channel?

joshuacox commented 7 years ago

sure I'll try discord out https://discord.gg/JvhYTR but feel free to open as many issues as you want here. This should be the best place for technical stuff, requests, support, etc.

joshuacox commented 7 years ago

1

for now this is the purpose of valve-start.sh vs valve-run.sh, notice that X-start.sh runs both X-install.sh and X-run.sh after that finishes. So if you know that the mounted volume has already been installed to then you can just put valve-run.sh as the script to run. This will skip the install and greatly reduce startup time.

2

funny enough this was addressed in a PR https://github.com/Thalhalla/dockarmaiii/pull/8 a few days ago, are you still having issues?

3

@jamessmoore has worked on this quite abit, can I get him to enlighten us on the whole mod string thing?

4

is this for the cluster-PW template?