Minecraft Server Manager
A complete, self-hosted control panel for Minecraft servers that run as Docker containers on the itzg/docker-minecraft-server image. It aims to rival commercial panels (Pterodactyl, Multicraft, AMP) in polish and capability while staying entirely free and local.
**Zero paid services. Everything runs on your machine, and your entire panel is one folder you can copy to migrate.**
🤖 Made with AI help: most of the code is written with Claude Code, and every feature is designed, reviewed and tested by a human. The details are in AI-DECLARATION.md.
| 🚀 Installation | ✨ Getting Started | 📜 Documentation | 🖼️ Screenshots | | -------------------------------- | --------------------------------------------- | ---------------------------------- | ------------------------------ |
💬 We now have a Discord!
Report bugs, suggest features, get help from real humans, and show off your servers.
There's a support forum, a showcase for your creations, and a dev corner if you want to contribute.
👥 The people who build MSM
Most of this panel was written by people who showed up and stayed.
Every one of them started with a single issue or a single pull request, and that is still how it
starts. Fix a typo, send a crash log, or pick something from
areas that need work. You will get help along the way,
and your face lands here.
These people made MSM better without writing any code. A careful bug report or a good idea is worth just as much here, and it puts you on this page too.
Features
- 🐳 Every server is its own resource-capped Docker container: create / start / stop / restart / rebuild / delete with graceful RCON stop and crash detection
- 🧙 Guided wizard: Simple or Advanced mode, every image env var explained in plain English
- 📌 Modpacks always pinned to an exact version, with explicit upgrades that offer a preview, pre-update backup, health monitoring, and one-click rollback
- 🧩 Five content registries in one browser: Modrinth, CurseForge, Hangar, SpigotMC, GitHub Releases (only CurseForge needs an API key)
- 🔗 Add by link: paste any project page, GitHub repo, slug, or direct jar URL
- 🗜️ Import anything: Modrinth
.mrpack, CurseForge exports, or your own zip of jars, with every jar identified and compatibility-checked - 🔒 Checksum-verified downloads (sha512 → sha256 → sha1 → md5), so a mismatch never reaches the server
- 📚 Shared sha256-deduplicated mod library, hard-linked into servers; custom mods survive pack updates
- 🖥️ Live console over WebSocket, RCON command bar, log filters, player quick-actions
- 👮 Player moderation: whitelist, ops, bans, IP bans, teleports, online via RCON and offline via JSON edits
- 💾 Save-safe backups with retention you set panel-wide or per server + cron schedules (restart / backup / RCON)
- 📜 Blueprints (
.mcserver.zip): portable server recipes you export, import anywhere, and get the same server from - 🔥 Crash forensics: auto-detected, parsed, suspects identified, plus one-click mclo.gs sharing and automated insights
- 🗺️ One-click BlueMap live map, served through the panel's authenticated proxy
- 📈 Storage analytics & panel-enforced disk quotas, playtime/deaths/mining analytics & scoreboard, inventory forensics, advisory x-ray investigation
- 🪄 Optional per-server chatbot (local/OpenAI-compatible LLM) with constrained in-game powers (docs)
- 🔔 Discord webhooks with per-event toggles and an Alerts category
- 👥 Multi-user roles (admin / operator / viewer) with per-server permissions + TOTP two-factor auth
- 🌐 Optional public status page, invite blocks, and generated client
.mrpackwith the server pre-added - 🧠 Pick-mods-first solver: choose mods, get the newest fully-compatible loader + MC version
📚 New here? The full documentation walks through every feature with screenshots: getting started, servers, modpacks, backups, two-factor auth, and more. The feature tour further down this page has the detailed version of the list above.
Installation
Requirements
- Node.js 24+ (current LTS) for the from-source install: uses the built-in
node:sqlite(flagless from Node 24), so there are
- Docker
\\.\pipe\docker_engine.
- macOS: Docker Desktop (/var/run/docker.sock).
- Linux: Docker Engine (/var/run/docker.sock; add your user to the docker group).
- A few GB of disk for server images + worlds.
🐳 Option 1: Docker (Linux hosts, Portainer, Dockge, compose)
A pre-built multi-arch image (amd64 + arm64) is published to GHCR on every release:
ghcr.io/anefzaoui/minecraft-server-manager:latest (or pin a version tag, e.g. :v0.14.1).
On a fresh Linux server, the installer does the whole thing: installs Docker if it's missing, writes
/opt/msm, starts the panel, and waits until it answers.
curl -fsSL https://raw.githubusercontent.com/anefzaoui/minecraft-server-manager/main/deploy/install.sh | sudo bash
Run it again any time to upgrade; it keeps your data, your .env, and any edits you made to the
compose file. --help lists the rest: --dir, --port, --bind 127.0.0.1 for a reverse-proxy
setup, --tag v0.14.1 to pin a version, and --uninstall.
Prefer to drive it yourself, or using Portainer/Dockge? Grab the docker-compose.yml from the repo root, set one variable, and start:
mkdir -p /opt/msm/data
echo "DATA_DIR_HOST=/opt/msm/data" > .env # ABSOLUTE host path for all panel data
docker compose up -d
Open http://your-host:25564. In Portainer/Dockge, paste the compose file as a stack and set
DATA_DIR_HOST in the stack's environment.
[!IMPORTANT]
The panel drives the host's Docker daemon through the mounted socket, and anything that holds
the Docker socket is root-equivalent on the host, so treat the panel's admin login accordingly and
never expose the UI raw to the internet. Docker Desktop (Windows/macOS) is not a target for this
mode; run the panel natively there.
How the containerized panel works, and what to know
- The panel drives the host's Docker daemon through the mounted
/var/run/docker.sockand creates
DATA_DIR_HOSTis required and must be the absolute host path of the directory mounted at
/data: bind mounts are resolved by the daemon against the host filesystem, so the panel
re-roots every path it hands to Docker from its container-local view onto that host path. Without
it the daemon would mount host directories that don't exist.
- The container binds to
0.0.0.0inside its own network namespace; publish127.0.0.1:25564:25564
25564:25564 if a reverse proxy on the host fronts the panel (then set TRUST_PROXY +
COOKIE_SECURE).
- Features that reach a sibling container directly - currently just the live map (BlueMap) -
host.docker.internal (not
127.0.0.1 - that's the panel's own loopback, not the host's). Whichever answers first is
cached. The bundled docker-compose.yml maps host.docker.internal via extra_hosts:
host.docker.internal:host-gateway (Docker Engine 20.10+) for the fallback path; a raw
docker run or a stack tool that doesn't read extra_hosts from the compose file needs the
equivalent --add-host=host.docker.internal:host-gateway flag, or set MAP_PROXY_HOST
yourself.
- Reverse-proxy setups (Pangolin, NGINX, Traefik…) where a server's Docker network is set
networks: block to the panel service in
docker-compose.yml, referencing it as external: true) so the direct container-IP path above
actually has a route - without that, the panel falls back to the host-published-port path,
which may not be reachable at all in a network topology built around bypassing host ports.
🖥️ Option 2: From source (any OS, incl. Windows/macOS)
git clone https://github.com/anefzaoui/minecraft-server-manager.git minecraft-server-manager
cd minecraft-server-manager
pnpm install # installs deps and builds the Tailwind CSS (postinstall)
pnpm run build # optional: also build the esbuild client-JS bundle (raw source is served otherwise)
cp .env.example .env # optional - all values have sane defaults
pnpm start # or: pnpm run dev (auto-restart + CSS watch)
Open http://localhost:25564. By default the panel binds to localhost only (127.0.0.1), so it's
reachable just from this machine; set PANEL_HOST=0.0.0.0 to reach it across your LAN. The first run
walks you through a system check, creating the admin account, and optional panel configuration (public
domain, CurseForge key, time zone). If Docker isn't running you still get the full UI, and the lifecycle
features light up when the daemon comes up.
If you start with a non-loopbackPANEL_HOST, first-run/setupis PIN-gated: a 6-digit PIN is
printed to the server console and must be entered before the admin account can be created.
You do not need to set anything in .env to start: on first run the panel generates a strong
random cookie secret (data/.session-secret) and a separate at-rest encryption key
(data/.secret-key). Set SESSION_SECRET yourself only if you want to control it (e.g. to share one
across replicas); the at-rest key is always machine-local, so keep data/.secret-key with your
backups.
⚙️ Option 3: Under a process manager (PM2 / systemd)
For a from-source install that should survive reboots. Gotcha with PM2: it launches apps
with whatever Node version started the PM2 _daemon_, and later switching your shell with nvm does
not change it. A restart can silently re-launch on the old version and fail the Node-24 preflight.
Pin the interpreter per app:
pm2 start src/server.js --name minecraft-server-manager --interpreter "$(nvm which 24)"
pm2 save
(or pm2 kill && pm2 resurrect to relaunch the whole daemon under your current default Node.)
🪟 Windows notes
- Docker Desktop must be running before you start/create servers.
- Share your project drive with Docker Desktop (Settings → Resources → File sharing) so bind mounts
- Bind mounts on Docker Desktop are slower than named volumes; the panel uses bind mounts anyway
Time zone & region: picked during first-run setup (auto-detected from your system) and changeable
in Settings. All dates and player-activity times display in the zone you choose.
Screenshots
![]() Server overview & controls: connect address, live usage, and the world-controls rail that rides along on every tab. |
![]() Guided create wizard: Simple or Advanced; every server.properties knob applied from the first start. |
![]() Admin chat: styled tellraw/say to everyone or one player: colors, bold/italic/underline, chat-style log. |
![]() Live console & RCON: streamed logs with level filters and a command bar with history. |
![]() Mods & plugins: pack-managed and custom mods, one-click toggle, five-registry search (Modrinth, CurseForge, Hangar, SpigotMC, GitHub Releases), zip import (Modrinth .mrpack, CurseForge exports, or your own jar collections). Every jar is identified and compatibility-checked, and every download is checksum-verified. |
![]() Worlds: reset/re-roll with a custom or random seed, duplicate, and a shared world library. |
![]() Settings: the full image env catalog with plain-English help, resource sliders, and a MOTD editor. |
![]() Backups: save-safe archives with retention classes and one-click restore. |
![]() History: every action is a structured event with its actor and captured log excerpts. |
![]() Custom chat commands: owner-defined !triggers (RTP, warp, console) with cooldowns & permissions. |
![]() Schedules: per-server and global cron tasks (restart / backup / RCON) with next-run previews. |
![]() Storage analytics: per-server usage, largest files, orphan detection, and panel-enforced quotas. |
![]() Blueprints: portable .mcserver.zip recipes; export a server, import it anywhere, get the same server. |
![]() Version compatibility: which future Minecraft versions your mods actually have builds for, per version, so an upgrade is only ever offered when the mods can follow. |
Why this over Pterodactyl, Crafty Controller, or AMP?
All three are capable general game panels. This one is **purpose-built for Minecraft on the itzg/docker-minecraft-server image**, so the parts that are fiddly elsewhere are first-class here:
- vs Pterodactyl: no separate Wings daemon, database server, or "egg"
- vs Crafty Controller: same free, self-hosted spirit, but every
.mcserver.zip blueprints.
- vs AMP: no per-machine licence and no paid tiers. **MIT-licensed
Not affiliated with any of them.
Features in depth
Core
- Multi-server lifecycle: create / start / stop / restart / rebuild / delete, with graceful
stop before container stop, health-aware status, and crash detection with backoff. A
server's game port can be changed later (how).
- Loader build choice: a server built from mods can pin a specific Fabric, Quilt, Forge, or
- Guided wizard: Simple mode (the common knobs) or Advanced mode exposing every environment
KEY=value escape hatch. Only non-default values are applied.
- Modpacks are always pinned: "latest" is resolved to a concrete version id at install time and
- Version compatibility before a version update: a mod-loader server's Mods → Versions tab checks every installed
- Any mod loader build, on demand: the same tab switches a Forge, NeoForge, Fabric or Quilt
- Custom-mod overlay: mods you add yourself are downloaded into a shared, sha256-deduplicated
.disabled; pack-managed mods use the image's exclusion mechanism), and
an update that turns out badly can be reverted to the previous build from the library.
- Five content sources, one browser: Modrinth, CurseForge, and (keyless) Hangar (PaperMC's
-sources/-javadoc sidecars skipped, ETag
caching so update checks barely touch the rate limit). All five feed search, add-by-link, the
update checker, and the one-click updater. Quilt servers automatically accept fabric-tagged builds.
- Add by link, from anywhere: paste a Modrinth/CurseForge/Hangar/SpigotMC project page, a
owner/repo works), a Modrinth slug, or a direct .jar URL -
the panel resolves the right build for the server's loader and MC version.
- Server-side
.mrpackimport: upload a Modrinth modpack and it's previewed and installed like
.mrpack can also seed server creation.
- Verified downloads: every install from a registry is streamed through the strongest checksum
- Crash analysis via mclo.gs: one click shares a crash report as an mclo.gs paste (always behind
- Console, logs & RCON: live console over WebSocket, ANSI rendering, search/level filters, a
- Player moderation: whitelist, ops (levels 1 to 4), bans, IP bans; via RCON while running and via
- Backups & schedules: save-safe archive/restore with free-space preflight and retention per
- Blueprints (
.mcserver.zip): a portable recipe of an instance. Full config (secrets
- Storage analytics & quotas: a background size-indexer walks
./data, caches sizes, and
- History & crash reports: every action (lifecycle, config diffs, mods, packs, backups, RCON,
- Accounts & two-factor auth: multi-user with admin / operator / viewer roles, refined per
Beyond the basics (all shipped, all self-hosted)
- Live world map: one click installs BlueMap matched to the server's loader, allocates a port,
- Analytics & scoreboard: vanilla stats ingested on a schedule (playtime, deaths, kills,
- Activity timeline: every log line classified (chat, joins, leaves, deaths incl. PvP,
- Inventory forensics: read any player's inventory/armor/ender chest from playerdata NBT,
- Investigation: advisory x-ray suspicion scoring from ore-discovery ratios vs the server
- Discord: webhook notifications (lifecycle, crashes, backups, updates, player actions) with
- Invites & client modpacks: a paste-ready invite block plus a generated client
.mrpackwith
- Pick-mods-first solver: choose the mods you want; the solver intersects Modrinth metadata to
- Public status page: optional unauthenticated
/status/per server: live status, MOTD,
- Public API: optional read-only
/api/v1, authenticated with admin-minted Bearer tokens that
Networking, ports & remote access
A fresh install is localhost-only: it answers only at http://localhost:25564 on the machine
it runs on. This section covers how to reach it from elsewhere and exactly which ports to open.
Ports at a glance
| What | Port(s) | Protocol | Open to the internet? |
| ------------------------ | -------------------------------------------- | --------- | ----------------------------------------- |
| Admin panel (web UI) | PANEL_PORT - default 25564 | TCP | Only behind TLS (reverse proxy), not raw |
| Game server (Java) | from PORT_GAME_START (25565) upward | TCP + UDP | Yes - this is how players connect |
| RCON | game port + 1000 (from 26565) | TCP | No - never. Panel-internal management |
| Bedrock / Geyser | from PORT_BEDROCK_START (19132) upward | UDP | Only if you run Bedrock |
| Live map (BlueMap) | auto-allocated | TCP | No - served through the panel's proxy |
The panel itself sits at 25564, one below the game runway, so game instances count cleanly
upward from 25565 with nothing interrupting the sequence. Game ports are then assigned first-free,
one game + RCON pair per server. Ten servers therefore occupy game 25565-25574 (TCP+UDP), RCON
26565-26574 (TCP), and, where Bedrock is enabled, 19132+ (UDP). The 1000-port RCON offset is
deliberate: it keeps RCON in a separate block so you can open a contiguous game range without ever
exposing RCON.
A port counts as taken if another server in the panel uses it (or is moving onto it right now), any Docker container on the host publishes it (even one the panel didn't create, running or stopped), or the operating system reports it in use. When the panel itself runs in Docker, that last check only sees the panel's own container, so a program running directly on the host, or a container using host networking, can still hold a port the panel thinks is free; the server then reports the port as in use when it starts.
To move a server later, open its Settings → Configuration tab and use the Game Port card: type a port, or press Use Next Free Port, then Save Port. RCON moves with it, to the port 1000 higher. The change applies right away. A running server asks first, then restarts on the new port (the world is saved first, and players reconnect on the new port). A stopped server simply gets its new port, used from its next start. If the server has other setting changes still waiting for Apply Changes, apply those first: the port change only rebuilds what already ran, so it can always put the server back. If the running server can't start on the new port (something took it in the meantime), the panel starts it again on its old port, the port is not changed, and the card and the server's history say why.
Admins may pick any port from 1024 up; other users pick from PORT_GAME_START upward. Either way the
port must leave room for RCON below 65535. RCON sits 1000 above the game port, so as long as the game
range you open to players is narrower than 1000 ports, RCON never lands inside it. The world and everything else in the data folder are untouched.
Why RCON must stay closed: RCON is a plaintext remote-admin protocol guarded only by a password.
The panel reaches it via docker exec _inside_ the container, so the host RCON port is never needed
from outside. Leave 26565+ blocked at the firewall.
Reach the panel from another machine
The panel binds to 127.0.0.1 out of the box. To listen on all interfaces, set in .env:
PANEL_HOST=0.0.0.0
PANEL_PORT=25564
Restart the panel so it re-reads the environment. Under PM2 you must pass --update-env, or
PM2 keeps the old value:
pm2 restart <id> --update-env # PM2 - --update-env is essential
or restart however you launched it
Confirm the bind address actually changed:
ss -tlnp | grep 25564 # want 0.0.0.0:25564, not 127.0.0.1:25564
Then open the panel port in both the host firewall and, on a VPS, your provider's separate cloud firewall (the one people forget):
sudo ufw allow 25564/tcp # ufw
sudo firewall-cmd --add-port=25564/tcp --permanent && sudo firewall-cmd --reload # firewalld
Open game ports for players
Open a range sized to how many servers you plan to run. Game ports are TCP and UDP: UDP carries the query protocol on the same port.
sudo ufw allow 25565:25584/tcp
sudo ufw allow 25565:25584/udp
sudo ufw allow 19132:19141/udp # Bedrock / Geyser - only if used
Do not add a rule for the RCON range (26565+).
Do it safely (recommended)
Exposing the raw panel port on the internet means logins travel over plain HTTP. Prefer one of:
- Reverse proxy with TLS: keep
PANEL_HOST=127.0.0.1, terminate HTTPS in front, and set
TRUST_PROXY=1 + COOKIE_SECURE=auto. Minimal Caddy:
mc.example.com {
reverse_proxy 127.0.0.1:25564
}
You then open only 80/443, never 25564.
- SSH tunnel: no exposure, no firewall change, just for you:
ssh -L 25564:127.0.0.1:25564 user@your-server # then open http://localhost:25564 locally
Configuration (.env, all optional)
| Variable | Default | Purpose |
| ---------------------------------------------------------------------------------------- | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| DATA_DIR | ./data | Root for all panel state (DB, server data, backups, library). |
| DATA_DIR_HOST | = DATA_DIR | Only when the panel runs in a container: the absolute host path of the DATA_DIR mount, used to re-root bind mounts for the host daemon. |
| MAP_PROXY_HOST | see note | Address the panel uses to reach sibling containers' host-published ports (currently just the live map). 127.0.0.1 bare metal; auto-switches to host.docker.internal when DATA_DIR_HOST is set (containerized panel - needs extra_hosts, see above). Override for rootless Docker/remote daemons. |
| PANEL_HOST / PANEL_PORT | 127.0.0.1 / 25564 | Web UI bind address + port. Localhost-only by default; set PANEL_HOST=0.0.0.0 for LAN access. |
| SESSION_SECRET | auto-generated | Signs session cookies. Auto-created and persisted at $DATA_DIR/.session-secret if unset. At-rest encryption uses a separate auto-generated $DATA_DIR/.secret-key, so rotating this no longer invalidates stored secrets. |
| TRUST_PROXY / COOKIE_SECURE / COOKIE_SAMESITE | - / - / lax | Set when behind a TLS-terminating reverse proxy. TRUST_PROXY (hop count, loopback, or IP/CIDR list - a bare true is deprecated and treated as 1 with a boot warning, because it trusts a spoofable X-Forwarded-For) is required for req.ip to see the real client, which the rate limiters key on. COOKIE_SECURE is true/false/auto (auto only works together with TRUST_PROXY; the panel warns at boot when it is set alone). COOKIE_SAMESITE is lax/strict/none; none requires COOKIE_SECURE. |
| RATE_LIMIT_API_PER_MIN / RATE_LIMIT_AUTH_PER_15MIN / RATE_LIMIT_PUBLIC_API_PER_MIN | 1200 / 100 / 120 | Per-client-IP request ceilings: all of /api, login / 2FA / setup POSTs, and per-token requests to the public /api/v1. 0 disables that limiter. A volume backstop on top of the per-account login lockout. |
| MSM_EXIT_ON_FATAL | - | 1/true/yes makes the post-boot runtime guard hard-exit on an uncaught exception/rejection instead of logging and staying up - for supervised deployments (systemd, Docker restart:). |
| DOCKER_HOST | auto-detected | Docker endpoint override for rootless Docker, Podman, or a remote daemon (per-OS socket/pipe otherwise). |
| CF_API_KEY | - | Optional CurseForge API key to seed on first run (also settable in the UI). Wrap in single quotes; CF keys often contain $. |
| GITHUB_TOKEN | - | Optional GitHub token to raise the unauthenticated API quota for the GitHub Releases content source (ETag caching keeps usage minimal either way). |
| MC_IMAGE_REPO | itzg/minecraft-server | Docker image repo for servers; override for a private mirror / air-gapped registry. |
| DEFAULT_HEAP_MB / DEFAULT_CONTAINER_MEMORY_MB / DEFAULT_DISK_QUOTA_GB | host-aware | Starting resource defaults for new servers. The memory pair adapts to the host's RAM when unset (heap ≈ 25% of RAM, container limit ≈ 1.5× that); the disk quota defaults to a flat 25 GB. |
| PORT_GAME_START / PORT_RCON_OFFSET / PORT_BEDROCK_START | 25565 / 1000 / 19132 | Port allocation scheme. |
| LOG_LEVEL | info | Log verbosity: fatal, error, warn, info, debug, trace, silent. Structured JSON to stdout. |
| LOG_PRETTY | auto (TTY in dev) | false forces JSON output; ignored in production. |
| SENTRY_DSN (+ SENTRY_ENVIRONMENT, SENTRY_TRACES_SAMPLE_RATE) | - | Optional error-reporting seam. Inert unless a DSN is set; the wiring in src/instrument.js is a no-op stub for now. |
Exposure: the panel binds to localhost by default. Set PANEL_HOST=0.0.0.0 for LAN access, and only
put it on the internet behind a reverse proxy with TLS (setTRUST_PROXY+COOKIE_SECURE). Auth is
mandatory from the first run.
The ./data directory: everything lives here
data/
.session-secret auto-generated cookie-signing secret (keep private; delete = rotate)
.secret-key auto-generated at-rest encryption key (keep with backups; delete = lose
stored API keys / RCON passwords / TOTP secrets)
panel.db SQLite database (node:sqlite, WAL)
servers/<id>/ bind-mounted as /data into each container (world, mods, configs…)
backups/<id>/ backup archives
backups/_panel/ panel-DB snapshots (VACUUM INTO, newest 14 kept)
blueprints/ .mcserver.zip exports
library/mods/ shared mod/plugin jars, deduplicated by sha256
library/modpacks/ pack archives
library/worlds/ world archives (the world library)
library/icons/ instance icons + cached mod icons
logs/<id>/events/ captured log excerpts linked from history events
logs/<id>/inventories/ player inventory snapshots (join/death)
tmp/ in-flight downloads (wiped on boot)
Copy data/ to another machine → you migrated the whole panel. Back it up like you'd back up a
world. Every file operation is contained to this root (path-guard enforced).
How the important things work
Two memory limits
- Java heap (
MEMORY): what Minecraft may use. - Container limit (Docker
HostConfig.Memory): the hard cap; hitting it OOM-kills the server.
"Memory used" settles at the heap size. That is not a leak. The image hands MEMORY to Java
as both the starting and the maximum heap, and Java fills a heap it was given up front within the
first minute of world generation, whether or not Aikar's or MeowIce's flags are on (they only make
it instantaneous). Measured on a Paper 1.21.1 server with a 2 GB heap and a fresh world, sampled
for three minutes after "Done" (each figure moved by under 50 MB in that time):
| Setting | Memory used |
| ------------------------------------------------------------- | ----------- |
| Default (MEMORY only), with or without a flag preset | ~2.6 GB |
| Aikar's flags plus -XX:-AlwaysPreTouch in Extra JVM options | ~1.95 GB |
| Aikar's flags plus INIT_MEMORY=512M ("Initial heap") | ~1.4 GB |
| No preset, INIT_MEMORY=512M | ~1.25 GB |
Turning off pre-touch only delays the fill: Java still works through the whole heap over time and never hands it back (a Forge 1.20.1 server with a 4 GB heap and no preset read 3.7 GB after a week with nobody on). A smaller Initial heap (Resources card on Settings → Configuration) is the setting that changes what Java asks for, so that is the lever if you want idle memory to follow real use; the trade-off is that Aikar's flags recommend equal heaps for the steadiest tick times. Java also needs memory outside the heap: about 0.5 GB on vanilla, 1.5-2 GB on a large modpack, which is what the headroom above is for.
The panel's meters mark where the heap sits on the container-limit scale and say so. The panel
subtracts disk cache like docker stats does; hypervisor dashboards often do not (Proxmox counts
the VM's cache as used, and since version 9 the VM's own overhead on the host too), so a VM's
summary page can read well above the panel for the same server.
Java version selection
The image does not pick Java for you. The panel maps MC version → image tag
(java8/16/17/21/25/latest) with a per-server override in Advanced settings.
GT New Horizons
GTNH is installed from its own release index rather than CurseForge, and the panel always pins an
exact pack version. Java is chosen per version from the index's own maxJavaVersion: GTNH 2.8.0 and
later run on Java 25 via the pack's bundled lwjgl3ify patches, older releases on Java 21 or 17.
Budget 6 GB of heap and 20 GB of disk to start; the wizard raises both for you. See the
modpacks guide for the full pack workflow.
Disk quotas are panel-enforced
Docker can't cap bind-mount disk usage, so a background size-indexer walks ./data, caches sizes in
SQ
... (README truncated for length)













