Geoff Bourne

Agreed, I wouldn't want an HTTP server running there. What I meant is that I seem to remember one that ran in-process with a very simple REST API.

Found it, this is what I remembered https://jolokia.org/. Specifically https://jolokia.org/reference/html/agents.html#jvm-agent

I'll have to look at what their API provides back. Also, I don't think a "local" URL will work since I'm assuming the URL needs to be something the client...

Thanks for doing that research. In that case, I'm thinking option 1 is the only thing that can be done. Like you said, 2 would be awesome but sounds very...

I think this is beyond the scope of what the container itself can do. The logs and attaching behavior are docker level things. Even the rcon access and output is...

I'm sorry, I'm afraid I can't help. After the container startup is finished (the [init] logs at the start) the process is handed off to the server and it's beyond...

Yeah I would generally lean towards option 1 but am also worried about possible overlap of backup runs. Specifically I would worry when one instance told the server to resume...

If lockfile usage is optional (off by default), then I am fine with that approach. My general concern was forcing users to declare a whole volume (which might be a...

Overall that looks great. I'd suggest collapsing the enable/location variables into one. Agreed, the content of the lock file becomes non-important. Container ID might still be good for debugging.

What you're attempting should be fine. It's actually running into a DNS problem since this is UDP to port 53 ``` lookup mc on 127.0.0.11:53: read udp 127.0.0.1:43190->127.0.0.11:53: read: connection...