Repository navigation
Moved container to new server - says I have more dependencies (some that don't make sense, like forge mods - it's a fabric server)? #4308
|
I've been using the docker-minecraft-server for about a year for a 1.20.1 Fabric server. That server was running out of space and on kind of crappy hardware, so I set up a new server, installed Docker Compose, and then zipped up and moved the container to the new server. After unzipping and running docker compose up -d on the new server it was failing to start, and then looking at the logs I'm seeing this: First, I don't understand why it was running fine on the old server with the same exact docker compose yaml file? Second, some of these look like they are Forge plugins, so that doesn't make any sense? What should I do? Thanks! EDIT: here is the compose.yaml file I've been using on the older server: Full Docker Compose Log: |
Replies: 2 comments 13 replies
|
I only have some guesses/questions. One guess is that the versions of the mods might have updated since the last restart of the old server. However that's a weak guess since the number of new dependencies is strange. One or two, sure, but not that many. How did you zip up the previous several exactly? I'm wondering if you zipped |
|
Unfortunately still a no-go trying all of that. First tried just commenting out wthit in the CURSEFORGE_FILES environment var, and when that didn't seem to get anywhere (was reading as this: then I tried adding betterend-forge, betterend-neoforge, and origins-forge to the list, but now I'm getting errors on all three of those: I'll start trying to go through and figure out if anything should be client side only. Just weird that it worked well on the old server as-is if that's the problem. |
I narrowed the copy of your compose to just the primary parts and it started up fine for me.
I changed two things: