Portainer Templates logo

Portainer Templates

McMyAdmin 2 McMyAdmin 2

Container

Other

McMyAdmin 2 is the leading web control panel and administration console for Minecraft servers.

Image details

Pulls: 3.7M
Architecture: amd64
Image size: 170 MB
User: linuxserver
Created: Oct 14, 2015
Updated: 7 years ago
Status: active

Configuration

Type
Container
Platform
linux
Image
linuxserver/mcmyadmin2:latest
Ports
8080:8080/tcp25565:25565/tcp
Volumes
/minecraft
Env vars
PUID=1000PGID=100
Restart
unless-stopped

Template by mikestraney

Standalone Install

Select an install method, to see config/commands for deploying McMyAdmin 2

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select McMyAdmin 2, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation.

THIS IMAGE IS DEPRECATED. We will no longer be making updates or rebuilding this image. The Dockerhub endpoint will stay online with the current tags for this software.
linuxserver.iolinuxserverurl
The LinuxServer.iolinuxserverurl team brings you another container release featuring easy user mapping and community support. Find us for support at:

linuxserver/mcmyadmin2

Docker PullshubDocker StarshubBuild Status
McMyAdminappurl combines minecraft with a web control panel and admin console so can take a little while to start up.
mcmyadminappurl

Usage

docker create --name=mcmyadmin \
-v <path to data>:/minecraft \
-e PGID=<gid> -e PUID=<uid> \
-p 8080:8080 -p 25565:25565 \
linuxserver/mcmyadmin2

Parameters

`The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side. For example with a port -p external:internal - what this shows is the port mapping from internal to external of the container. So -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 http://192.168.x.x:8080 would show you what's running INSIDE the container on port 80.`
  • -p 8080:8080 - Mcmyadmin webui port.
  • -p 25565:25565 - Minecraft game server port.
  • -v <path to data>:/minecraft - The location to store all your permanent files server jars\maps\configs and more.
  • -e PGID numeric GroupID - see below for explanation
  • -e PUID numeric UserID - see below for explanation

It is based on ubuntu xenial with s6 overlay, for shell access whilst the container is running do docker exec -it mcmyadmin /bin/bash.

User / Group Identifiers

Sometimes when using data volumes (-v flags) permissions issues can arise between the host OS and the container. We avoid this issue by allowing you to specify the user PUID and group PGID. Ensure the data volume directory on the host is owned by the same user you specify and it will "just work" ™.
In this instance PUID=1001 and PGID=1001. To find yours use id user as below:
$ id <dockeruser>
  uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)

Setting up the application

Minimum of 2GB of ram required for this container to work properly.
After starting the container, log into the Web UI as the admin user with the password password and change the password. You should also consider serving the admin UI over https.

Info

  • Shell access whilst the container is running: docker exec -it mcmyadmin /bin/bash
  • To monitor the logs of the container in realtime: docker logs -f mcmyadmin

  • container version number

docker inspect -f '{{ index .Config.Labels "build_version" }}' mcmyadmin
  • image version number

docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/mcmyadmin2

Versions

  • 14.12.17: Fix continuation lines.
  • 03.03.17: Rebase to ubuntu xenial.
  • 13.02.16: Switched to Java 8
  • 14.10.15: Removed Support for spigotmc
  • 01.07.15: Fixed docs
  • 26.06.15: Updated Docs and finalized design.

Serve McMyAdmin 2 on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying mcmyadmin-2.example.com to http://mcmyadmin2:8080

Add this to your Caddyfile

mcmyadmin-2.example.com {
	reverse_proxy http://mcmyadmin2:8080
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs mcmyadmin2
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:8080 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :8080
  • Stop the other service, or pick a different host port. In 8080:8080 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:8080. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, mcmyadmin2 can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8080

Image won't pull

Test the pull directly on the host: docker pull linuxserver/mcmyadmin2:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect mcmyadmin2 --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

McMyAdmin 2 runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything McMyAdmin 2 needs bundled into one download. This template pulls linuxserver/mcmyadmin2:latest, which Docker fetches once (about 170 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. McMyAdmin 2's comes from Docker Hub, published by linuxserver.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, so it runs on regular x86 PCs and servers, though not ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 8080:8080 means it's reachable on port 8080 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:8080 in a browser. It opens:

  • 8080:8080, likely the web interface
  • 25565:25565

Volumes

A volume is where McMyAdmin 2 keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /minecraft as a volume Docker manages for you

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. McMyAdmin 2 takes 2 of them, all with defaults you can leave alone or tweak:

  • PUID, defaults to 1000
  • PGID, defaults to 100

Restart policy

The restart policy here is unless-stopped, so Docker restarts McMyAdmin 2 after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Users and permissions

The PUID and PGID settings tell it which user and group to act as on your host. Point them at your own account (find yours with id $USER) so the files it writes into your mounted folders come out owned by you rather than root.

Networking

Nothing custom is set, so McMyAdmin 2 sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container mcmyadmin2. That's what you'll spot in the containers list and use in commands like docker logs mcmyadmin2.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set McMyAdmin 2 up. Add the template list to Portainer once, then deploying McMyAdmin 2 is a click rather than a wall of config.