Issue using compose for prominence 2 #3385
Answered
by
itzg
Clownsonged
asked this question in
Q&A
-
Using the below docker compose and getting the following error when deploying the stack.
Error log-
|
Beta Was this translation helpful? Give feedback.
Answered by
itzg
Apr 1, 2025
Replies: 1 comment 1 reply
-
I see what you mean. The example failed in the same way for me. I thought upgrading the modpack would help, but it turned out I needed to force-include luna since it must be tagged as a client-only mod by the CurseForge metadata. This ended up working for me: services:
mc:
image: itzg/minecraft-server
ports:
- "25565:25565"
environment:
EULA: "true"
MODPACK_PLATFORM: AUTO_CURSEFORGE
# Allocate API key from https://console.curseforge.com/
# and set in .env file making sure to double up dollar signs, such as
# CF_API_KEY=$$2a$$10$$....
# Refer to https://docker-minecraft-server.readthedocs.io/en/latest/types-and-platforms/mod-platforms/auto-curseforge/#api-key
CF_API_KEY: ${CF_API_KEY}
CF_PAGE_URL: https://www.curseforge.com/minecraft/modpacks/prominence-2-rpg
CF_FILENAME_MATCHER: "3.1.7"
CF_EXCLUDE_MODS: |
config-menus-forge
welcome-screen
CF_FORCE_INCLUDE_MODS: |
luna
MEMORY: 4G
volumes:
- mc-data:/data
volumes:
mc-data: {} |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
Clownsonged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I see what you mean. The example failed in the same way for me. I thought upgrading the modpack would help, but it turned out I needed to force-include luna since it must be tagged as a client-only mod by the CurseForge metadata. This ended up working for me: