Image Variants
Gate offers two Docker image variants to suit different use cases:Standard Image
ghcr.io/minekube/gate:latestMinimal distroless image for most use cases. Smaller footprint and enhanced security.JRE Variant
ghcr.io/minekube/gate/jre:latestIncludes Java Runtime Environment. Required for Bedrock Edition support with Geyser.Use the JRE variant (
ghcr.io/minekube/gate/jre:latest) if you need:- Bedrock Edition support (cross-play with mobile, console, Windows Bedrock)
- Gate’s managed Geyser mode
- Java runtime in your container
Version Tags
Gate images support multiple version tags:latest- Latest stable release (recommended)0.42.2- Specific version tags6d3671c- Commit SHA tags for edge builds
main branch is built and pushed with both latest and the commit SHA tag.
Docker Run
Basic Usage
Run Gate with default settings:-it- Interactive mode with pseudo-TTY (see logs in real-time)--rm- Automatically remove container when it exits-d- Use instead of-itto run in detached mode
With Configuration File
Mount your customconfig.yml:
The JRE variant example includes UDP port 19132 for Bedrock Edition connections.
With Minekube Connect
Integrate with Minekube Connect for managed hosting:- Environment Variable
- Volume Mount
The
CONNECT_TOKEN environment variable takes precedence over connect.json file.Docker Compose
Basic Setup
Create adocker-compose.yml file:
Complete Example with Minecraft Servers
Gate includes a complete example that configures Gate with two Minecraft servers:Review the configuration
The example includes:
- Gate proxy with network configuration
- Two Pufferfish servers (server-0, server-1)
- Volume mounts for server data
docker-compose.yml
Podman
Gate works seamlessly with Podman as a Docker alternative:Troubleshooting
Error: "denied" when pulling image
Error: "denied" when pulling image
If you see:You may be logged in with an expired GitHub token. Solution:GitHub Container Registry doesn’t require authentication for public images. An expired token is worse than no token.
Container exits immediately
Container exits immediately
Check logs for errors:Common causes:
- Invalid configuration file
- Port already in use
- Missing required volumes
Cannot connect to proxy
Cannot connect to proxy
Verify:
- Ports are correctly mapped (
-p 25565:25565) - Firewall allows connections
network_mode: hostis used (easier for beginners) or ports are properly exposed- Container is running:
docker ps
Configuration changes not taking effect
Configuration changes not taking effect
Restart the container after config changes:
Best Practices
Use specific version tags
Pin to specific versions in production instead of
latest:Mount configuration as read-only
Prevent accidental modifications:
Use docker-compose for multi-container setups
Manage Gate and backend servers together with defined dependencies and networking.
Set resource limits
Control memory and CPU usage:
Next Steps
Kubernetes Deployment
Scale Gate in Kubernetes clusters
Configuration
Customize Gate for your network

