Install Minecraft Server Using Docker Compose

This article is for those looking for a detailed and straightforward guide on installing Minecraft Server using Docker Compose.
A Minecraft Server is a player-owned or business-owned multiplayer game server for the 2009 Mojang Studios video game Minecraft. In this context, the term βserverβ often colloquially refers to a network of connected servers, rather than a single machine.
πΎ You can find the repository used in this guide on GitHub.
CAUTIONYou will need A-type records in the external DNS zone, which point to the IP address of your server where Minecraft Server is installed. If you have created these records recently, you should wait before starting the installation of the services. Full replication of these records between DNS servers can take from a few minutes to 48 hours or even longer in rare cases.
NOTEAlternatively, you can use the public static IP address of your server to connect directly.
IMPORTANTDocker Engine and Docker Compose must be installed on the server.
For a step-by-step guide on installing Docker Engine on Ubuntu Server, see Install Docker Engine and Docker Compose on Ubuntu Server
IMPORTANTOpenSSH must be installed on the server, and port 22 must be open in order to be able to connect to the server using the SSH protocol.
To install OpenSSH on the server you can use the command:
sudo apt install openssh-server
NOTETo connect to the server from a Windows system, you can use tools like PuTTY or MobaXterm.
NOTEThis guide walks you through connecting to a server with the iTerm2 terminal emulator on macOS.
CAUTIONYou will need to open the following TCP ports for access to the services:
- TCP port 25565 - to connect Minecraft clients to the server.
We connect to the server on which Minecraft Server is planned to be installed.
Now it is necessary to create a network for your services.
We create a network for Minecraft Server using the command:
docker network create minecraft-server-network
Next, you need to clone the repository that contains the configuration files, which include all the necessary conditions for Minecraft Server to work.
You can clone the repository using the command:
git clone https://github.com/heyvaldemar/minecraft-server-docker-compose.git
Navigate to the directory with the repository using the command:
cd minecraft-server-docker-compose
Next, you need to change the variables in the .env
file according to your requirements.
NOTEThe
.env
file andplugins
folder should be in the same directory asminecraft-server-docker-compose.yml
.
Now letβs start Minecraft Server with the command:
docker compose -f minecraft-server-docker-compose.yml -p minecraft-server up -d
CAUTIONTo connect to your Minecraft server, enter the domain name into the Minecraft client. This domain name should point to the IP address of your server where the Minecraft Server is installed. Alternatively, you can use the public static IP address of your server to connect directly.
CAUTIONBefore using a domain name, ensure you have set up A-type records in your external DNS zone that point to this IP address. If youβve recently created these records, itβs advisable to wait before starting the installation of the services. DNS record propagation can vary, taking anywhere from a few minutes to 48 hours, and in rare cases, even longer.
Patreon Exclusives
π Join my Patreon and dive deep into the world of Docker and DevOps with exclusive content tailored for IT enthusiasts and professionals. As your experienced guide, I offer a range of membership tiers designed to suit everyone from newbies to IT experts.
Tools I Personally Trust
If youβre building things, breaking things, and trying to keep your digital life a little saner (like every good DevOps engineer), these are two tools that I trust and use daily:
πΈ Proton VPN - My shield on the internet. It keeps your Wi-Fi secure, hides your IP, and blocks those creepy trackers. Even if Iβm hacking away on free cafΓ© Wi-Fi, I know Iβm safe.
π Proton Pass - My password vault. Proper on-device encryption, 2FA codes, logins, secrets - all mine and only mine. No compromises.
These are partner links - you wonβt pay a cent more, but youβll be supporting DevOps Compass. Thanks a ton - it helps me keep this compass pointing the right way π
Gear & Books I Trust
π Essential DevOps books
π₯οΈ Studio streaming & recording kit
π‘ Streaming starter kit
Social Channels
π¬ YouTube
π¦ X (Twitter)
π¨ Instagram
π Mastodon
π§΅ Threads
πΈ Facebook
π¦ Bluesky
π₯ TikTok
π» LinkedIn
π£ daily.dev Squad
βοΈ Telegram
π GitHub
Community of IT Experts
πΎ Discord
Refill My Coffee Supplies
π PayPal
π Patreon
π₯€ BuyMeaCoffee
πͺ Ko-fi
π GitHub
β‘ Telegram Boost
π Bitcoin (BTC): bc1q2fq0k2lvdythdrj4ep20metjwnjuf7wccpckxc
πΉ Ethereum (ETH): 0x76C936F9366Fad39769CA5285b0Af1d975adacB8
πͺ Binance Coin (BNB): bnb1xnn6gg63lr2dgufngfr0lkq39kz8qltjt2v2g6
π Litecoin (LTC): LMGrhx8Jsx73h1pWY9FE8GB46nBytjvz8g
Is this content AI-generated?
No. Every article on this blog is written by me personally, drawing on decades of hands-on IT experience and a genuine passion for technology.
I use AI tools exclusively to help polish grammar and ensure my technical guidance is as clear as possible. However, the core ideas, strategic insights, and step-by-step solutions are entirely my own, born from real-world work.
Because of this human-and-AI partnership, some detection tools might flag this content. You can be confident, though, that the expertise is authentic. My goal is to share road-tested knowledge you can trust.