FTB Skies 2 Aero

Dedicated server for the FTB Skies 2: Aero modpack (Minecraft 1.21.1, NeoForge, Java 21), a skyblock pack built around airships.

  • Game Servers
  • Tools & Utilities
Dedicated server for the FTB Skies 2: Aero modpack (Minecraft 1.21.1, NeoForge, Java 21), a skyblock pack built around airships. The Docker image ships Java 21 and the official FTB server installer, so the modpack downloads itself on first start with no manual setup. Operators, MOTD, world name and Java memory are set through the variables, and FTB_VERSION_ID selects the modpack version. Built for Minecraft server hosts who want a ready-to-run FTB Skies 2: Aero server.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

37/100 Low

Maintained
72last commit 3 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
106 GB minimum RAM

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2026-10-19
License
MIT
Activity
rising

Checked 3 days ago - source: GitHub (JonaxScript/ftb-skies-2-aero-docker)

Resources & Compatibility

Minimum requirements: 6 GB RAM, 1.26953 GB disk. ARM (e.g. Raspberry Pi) is not supported.

Checked 3 days ago - source: Docker Hub image tags and published docs

First-install notes

  • First start, EULA and updates On first start the container downloads the newest modpack (about 1.3 GB) into /data using the official FTB server installer, taking a few minutes; afterwards the server starts right away. Set EULA=true to accept the Minecraft EULA before the server will run, and to update later enter the new version in FTB_VERSION_ID. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How long does the first start take?

The first start installs about 1.3 GB of the modpack into /data and can take a few minutes. The first server start including world generation takes a few more minutes. It is ready when the logs show Done and the help prompt.

Where are the world and server files stored?

The server stores the world and all server files in the /data directory, which maps to the appdata folder on Unraid or a Docker volume. Back up that directory to preserve the server.

Are image updates and modpack updates the same?

No, modpack updates are separate from image updates. Updating the image keeps the world and server files in the appdata folder.

What should I set if I use a bind mount for data?

Use PUID and PGID set to your own user and group IDs. This makes the files belong to you instead of the container default user.

What stop timeout do the examples use?

The examples configure a 120-second stop timeout, written as stop_grace_period: 2m in Docker Compose.

Answers sourced from github.com

Community

Collected 2 days ago - public community threads