Skip to content

feat: add MC Controller template - #1177

Merged
Siumauricio merged 3 commits into
Dokploy:canaryfrom
Nargor:feat/add-mc-controller-template
Oct 8, 2026
Merged

Siumauricio merged 3 commits into
Dokploy:canaryfrom
Nargor:feat/add-mc-controller-template

Conversation

@Nargor

@Nargor Nargor commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

What is this PR about?

Adds MC Controller, a self-hosted panel for creating and managing multiple Minecraft servers: Vanilla, Fabric, Forge, NeoForge, Paper, Spigot, Bukkit, and CurseForge.

The template uses a persistent named volume and Docker socket access so the panel can create Minecraft containers and publish their individual game ports.

Validation

  • Read the repository contribution requirements
  • Ran node build-scripts/generate-meta.js --check (533 templates validated)
  • Validated the Compose configuration
  • Tested controller setup and creation of a Minecraft child container using a Docker named volume

Deployment notes

The panel itself is exposed through Dokploy on port 3000. Minecraft child containers publish ports directly on the Docker host; operators must allow the configured Minecraft port range in the firewall/security group.

Docker socket access is required for this application and should be protected with an administrator account and HTTPS.

@github-actions

github-actions Bot commented Sep 22, 2026 •

Copy link
Copy Markdown
built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
templates ✅ Ready (View Log) Visit Preview f05bb6b

busybox wget resolves localhost to ::1 first, but Nitro listens on
0.0.0.0 (IPv4 only), so the healthcheck always failed. The container
never became healthy and Traefik never routed the domain (404).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Siumauricio

Copy link
Copy Markdown
Contributor

Pushed a fix: the healthcheck used localhost, which resolves to IPv6 while the app listens on IPv4 only, so the container never became healthy (404). It now probes 127.0.0.1.

Approved, thanks!

@Siumauricio
Siumauricio merged commit 354311d into Dokploy:canary Oct 8, 2026
4 checks passed

This branch was successfully deployed

1 active deployment
Preview — f05bb6b3 Deployed Oct 8, 2026 by github-actions[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants