itzg / itzg/docker-minecraft-bedrock-server

Error with PageSize Configuration When Running Minecraft Bedrock Server in Docker

Open
#380 7 comments 0 reactions 0 assignees View on GitHub
discussion
Dominant language
Shell
Stars
1.9k
Forks
302
Avg merge
2h 26m
Merged PRs (30d)
2

Description

Hello,

I encountered an issue while trying to run a Minecraft Bedrock server using the `itzg/minecraft-bedrock-server` Docker image. Here are the steps I followed, the error message I received, and my system information.

**Command Used:**
docker run -it --rm -e EULA=TRUE -p 19132:19132/udp -v mc-bedrock-data:/data itzg/minecraft-bedrock-server /bin/bash

**Error Message:**
DEBU[0000] Using /data to match uid and gid
DEBU[0000] Resolved UID=0 from match path
DEBU[0000] Resolved GID=0 from match path
Looking up latest version...
Starting Bedrock server...
Error: PageSize configuration is wrong: configured with 4096, but got 65536

**System Information:**
- Output of `getconf PAGESIZE`: 65536
- OS Details:
NAME="CentOS Linux"
VERSION="7 (AltArch)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (AltArch)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

I am unsure about the cause of this `PageSize` configuration error and how it relates to my system's configuration. This issue occurs during the server startup process.

Could anyone provide insights into what might be causing this error and how to resolve it on my specific system?

Thank you in advance for your assistance.

Best regards,
majiajun7

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue with the reported docker run command and the displayed CentOS system configuration, then trace the image's startup path to where the PageSize error is emitted. The issue names no files or tests; done would require an identified cause and a verified resolution or a clearly documented system limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.