docker-minecraft-server: ATM10 errors I that seem obvious but can't get past
Sorry if this is a repeat question with all the mods, but I’ve tried removing/downgrading mods like allthewizard gear and sodium-extra but I can not get this server to work. Also a crash report is not being generated which I am used to so commented out always on for clear end point of logs.
Docker compose file
services:
mc:
image: itzg/minecraft-server
tty: true
stdin_open: true
ports:
- "25568:25565"
#restart: unless-stopped
environment:
CF_API_KEY: <key>
EULA: "TRUE"
TYPE: "AUTO_CURSEFORGE"
CF_PAGE_URL: https://www.curseforge.com/minecraft/modpacks/all-the-mods-10/
CF_FORCE_SYNCHRONIZE: TRUE
#CF_EXCLUDE_MODS: |
# sodium_extra
# sodium
# allthewizardgear
# betterdungeons
INIT_MEMORY: 5G
MAX_MEMORY: 18G
SEED: <seed>
OPS: <names>
KEEP_INVENTORY: "TRUE"
WHITELIST: "TRUE"
WHITELIST_USERS: <names>
ALLOW_FLIGHT: "TRUE"
SLEEP_PERCENT: "0" # Add this line to set sleep percent to zero
volumes:
# attach the relative directory 'data' to the container's /data path
- ./data:/data
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 32 (13 by maintainers)
And the merged example https://github.com/itzg/docker-minecraft-server/tree/master/examples/atm10
Yeah, I had already updated that locally. So I created a PR for an example. 1.17 also had some issues with the
shaderpacksfolder in the packs overrides folder. So my example shows that as well.Here is mine that’s currently running 1.12, but I don’t expect any issues upgrading to 1.13 which was recently released:
@rhullah I did actually. I think the CF_EXCLUDES_MODS in the link that that itzg posted above was the thing that got me over the hump.