Logs not printing through golang console and server not controllable - dumb-init issue? about openttd-jgrpp HOT 5 CLOSED

It looks like this may be due to the container command script (openttd.sh) containing a hashbang: #!/bin/sh

Could the process for the shell instead of the OpenTTD process become associated with the init background daemon?

from openttd-jgrpp.

Heya, sorry, this issue must have completely slipped under my radar...
I haven't used Docker on Windows in years, so reproducing the issue on my end may be a little tricky - I noticed that you invited me to a repo some time ago, were you able to get the issue fixed there?

On another note: I do remember the process of getting the console to properly work, even on Linux, to be quite involved and I sadly don't quite remember it anymore. I'll try to dig through my former server setup and maybe I can even try to improve the scripts here.

I tend to be quite busy though so no promises that that'll happen soon, I just happened to pick up OpenTTD again for the moment 😅

from openttd-jgrpp.

Hey @willnwalker, this is actually due to a slight misunderstanding in how the containers work. The server logs are printed from the openttd container, whereas the console container was just meant to be a sidecar container to easily run openttd-admin - this wasn't clearly communicated in documentation though. I've submitted a PR #9 that instead bundles openttd-admin with the image and clarifies usage a bit.

from openttd-jgrpp.

Heya @willnwalker, I just merged the PR mentioned above, if you have further questions or problems feel free to reopen this issue :)

from openttd-jgrpp.

Hey @willnwalker, this is actually due to a slight misunderstanding in how the containers work. The server logs are printed from the openttd container, whereas the console container was just meant to be a sidecar container to easily run openttd-admin - this wasn't clearly communicated in documentation though. I've submitted a PR #9 that instead bundles openttd-admin with the image and clarifies usage a bit.

Thanks for the clarity, I thought I was missing something! I did notice that the go container was just sitting there, not wired to anything. Thanks for this latest PR!

@ghostlydilemma If you're still into the game check out the jgr server channels in the official discord

Those container instances are deployed using https://github.com/pterodactyl "eggs", punnily called yolks:
https://github.com/pterodactyl/yolks

from openttd-jgrpp.