New to using your docker image. I have experience with java servers but not bedrock ones.
My question is: As the log to stdout seems quite limited, I wish to see what is written in a log file. Specifically i am looking for failed logins due to whitelist mismatch.
My Podman Compose looks like this:
services:
app:
image: itzg/minecraft-bedrock-server:stable
restart: unless-stopped
ports:
- 19132:19132/udp
volumes:
- /mc_data:/data
environment:
- EULA=true
- SERVER_NAME="MYSERVERNAME"
- SERVER_PORT=19132
- WHITE_LIST=true
- ENABLE_CONTENT_LOGGING=true
- CONTENT_LOG_FILE_ENABLED=true
- DEBUG=true
and i also set content-log-file-enabled=true and content-log-console-output-enabled=true in properties.json
The server prints
[2026-05-25 20:58:27:698 INFO] Content logging to console is enabled.
[2026-05-25 20:58:28:312 INFO] Content logging to disk is enabled. Writing log to: ContentLog2026-05-25_20-58-28
[2026-05-25 20:58:28:313 INFO] Opening level 'worlds/Bedrock level/db'
Yet when i attach to the container and execute find find -type d -name "*Content*" -print and find -name "*Content*" -print it turns out empty.
Does the bedrock server simply not write logs on denied access due to whitelist (and never creates a logfile) or is it lost somewhere?
Thank you in advance!
New to using your docker image. I have experience with java servers but not bedrock ones.
My question is: As the log to stdout seems quite limited, I wish to see what is written in a log file. Specifically i am looking for failed logins due to whitelist mismatch.
My Podman Compose looks like this:
and i also set
content-log-file-enabled=trueandcontent-log-console-output-enabled=trueinproperties.jsonThe server prints
Yet when i attach to the container and execute find
find -type d -name "*Content*" -printandfind -name "*Content*" -printit turns out empty.Does the bedrock server simply not write logs on denied access due to whitelist (and never creates a logfile) or is it lost somewhere?
Thank you in advance!