
      <p>Provisioning is a single API call away. The Fastify route validates input, selects a port, and asks Dockerode to create + start the container.</p>

      <h2>What we set at create time</h2>
      <ul>
        <li><strong>Image:</strong> Java or Bedrock, chosen by product</li>
        <li><strong>Volumes:</strong> bind host <code>/mc-servers/{name}</code> to container <code>/data</code></li>
        <li><strong>Ports:</strong> Java <code>25565/tcp</code>, Bedrock <code>19132/udp</code> with host port mapping</li>
        <li><strong>Env:</strong> <code>EULA=TRUE</code>, <code>SERVER_NAME</code>, <code>MAX_PLAYERS</code>, etc.</li>
        <li><strong>Restart:</strong> <code>unless-stopped</code> for resilience</li>
      </ul>

      <h2>Graceful stop & logs</h2>
      <ul>
        <li>Stop: <code>container.stop()</code> after sending <code>say</code>/save via exec if needed</li>
        <li>Logs (Java): <code>exec</code> <code>cat /data/logs/latest.log</code> and stream back</li>
      </ul>

      <h2>Health & stats</h2>
      <ul>
        <li>Stats endpoint aggregates <code>docker.stats</code> (CPU %, RSS) + host load average</li>
        <li>Used by scheduler to place new servers on the best node</li>
      </ul>
    

GlitchNode Blog

On-Demand Provisioning with Dockerode + Fastify

What we set at create time

Graceful stop & logs

Health & stats