A Docker container for running a Minecraft Java Paper server with Geyser and Floodgate, enabling Bedrock players to join.
Legendary Java Minecraft Geyser Floodgate is a Docker container that sets up a Minecraft Java Edition server with the Paper optimization, plus Geyser and Floodgate plugins to enable Minecraft Bedrock Edition players to join. It solves the problem of running a cross-play server by packaging everything needed into a single, easy-to-deploy container with automated management features.
Minecraft server administrators, hobbyists, and developers who want to run a self-hosted, cross-play server supporting both Java and Bedrock clients, especially those using Docker or Kubernetes for deployment.
Developers choose this because it provides a pre-configured, production-ready container that handles cross-play setup, automatic updates, and backups out of the box, saving time over manual server configuration and ensuring compatibility across platforms like Raspberry Pi and cloud environments.
Legendary Java Minecraft + Geyser + Floodgate + Paper Dedicated Server for Docker allowing Bedrock players to connect to a Java server
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Pre-installs and configures Geyser and Floodgate, allowing Bedrock players to join Java servers without manual plugin setup, as highlighted in the features list.
Updates to the latest Paper version on start and performs rolling backups on restart, reducing administrative work through environment variables like BackupCount.
Supports Docker on ARM devices like Raspberry Pi and includes Kubernetes manifests, enabling deployment across diverse hardware and cloud environments.
Plugins are installed by dropping .jar files into the plugins folder, with the container handling restarts, as described in the Plugins section.
The README warns of extra steps needed for Oracle Virtual Machines and Hyper-V due to networking issues, which can complicate deployment for some users.
Automatic updates on start might introduce instability, and while version pinning is possible via environment variables, there's no built-in scheduling for updates.
Terminal features are unavailable in Kubernetes mode, hindering real-time server management and troubleshooting, as noted in the Kubernetes usage section.