Replies: 1 comment 9 replies
-
It sounds like you need to pin a specific version/file of that modpack. (I only skimmed since the wall of text seems to have nothing to do with docker or this image) |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey all, I HAD a server set up and working well running this modpack
Last night, while attached to the Docker container, I stupidly hard-stopped the server with CTRL+C.
In Portainer, I simply restarted the container thinking it would just restart the server and everything would be back to normal.
The server seemed to start normally, but when I tried to join I would be met with a huge wall of text that could not be closed upon loading the world.
After some digging it seemed that it was caused by a modpack version mismatch between the client and the server, so I thought I'd just recreate the container thinking it would just redownload the latest version of the modpack.
I tried to just recreate the container with Portainer and, for reasons I'm not sure of, it only deleted the container without recreating it.
I'm trying to recreate it manually how I had it set up before, but I'm getting errors.
Here's the ENV variables I configured in Portainer:
Here's the log:
Any help would be greatly appreciated because I am at a loss and my friends are rioting at my door.
Edit:
Could be of note:
I've configured the new container to use the same volume/directory of the old volume, within which nothing has changed since the problems started.
Beta Was this translation helpful? Give feedback.
All reactions