On each first boot, the code to generate server.properties seems to hang. After Ctrl-C of ansible, either local or remote, I find that there are commands to echo stop to the socket hanging and minecraft itself is running, apparently directly from ansible rather than from systemctl. I gather that therefore the named pipe is not running, and therefore minecraft will not exit.
I am able to use the role to achieve infrastructure as code, but not fully automate. Since the server is for my kids, this is adequate.
On each first boot, the code to generate
server.properties
seems to hang. After Ctrl-C of ansible, either local or remote, I find that there are commands to echo stop to the socket hanging and minecraft itself is running, apparently directly from ansible rather than from systemctl. I gather that therefore the named pipe is not running, and therefore minecraft will not exit.I am able to use the role to achieve infrastructure as code, but not fully automate. Since the server is for my kids, this is adequate.