[init] ERROR: Modpack missing start script and unable to find Forge jar to generate one

[Fruchtmolke]

Greetings,

me and a friend have trouble getting a TNP 5 Limitless Modpack running. We use the newest docker, docker compose and portainer versions and we use the following script which you provided.

docker run -d -v /home/docker/volume:/data -e TYPE=CURSEFORGE -e CF_SERVER_MOD=https://mediafiles.forgecdn.net/files/3872/243/Limitless-5-2.14.0.zip -p 33444:33444 -e EULA=TRUE --name minecraft itzg/minecraft-server

We tried the version : [Limitless 5 - v2.14.0] And also: [LL5 Full Server Files - v2.14.0]

This is the output we are getting. I hope you can hel us out here. Would be really appreciated. I'm sure i'm just stupid and missing something important.

[GeoDerp]

From my experience, it could likely be the wget issue. Try downloading the zip manually, validating it's the right file, then placing it into the root of the data volume /home/docker/volume

then run: docker run -d -v /home/docker/volume:/data:Z -e TYPE=CURSEFORGE -e -p 33444:33444 -e EULA=TRUE CF_SERVER_MOD=Limitless-5-2.14.0.zip --name minecraft itzg/minecraft-server note: :Z may not be needed

[itzg]

You might need to instead use it as a GENERIC_PACK such as https://github.com/itzg/docker-minecraft-server/blob/master/examples/docker-compose-generic-pack-atm7.yml

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open.

[TerminalFault]

@itzg - I ran into the same issue as above and used GENERIC_PACK which loaded it up fine. However I ran into one issue where the EULA wouldn't update even though it was set in the config. Launching the container and updating the EULA manually worked fine though. Thoughts?

Relevant Config:

environment:
  EULA: "true"
  TYPE: FORGE
  VERSION: 1.18.2
  FORGEVERSION: 40.1.73
  GENERIC_PACK: /modpacks/tnp5.zip

[itzg]

@TerminalFault how did you determine it wasn't updating the EULA?

[TerminalFault]

@itzg Nothing too deep honestly. It was looping with:

[23:53:41] [main/INFO]: You need to agree to the EULA in order to run the server. Go to eula.txt for more info.
2022-08-27T23:53:41.980-0400    INFO    mc-server-runner        Done
[init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 9 1000 1000 4096 Aug 27 23:53 /data'

I tried killing it and starting over with the same config and had the same thing happened. While it was booting I took a look inside the container and checked the EULA which was still set to FALSE. I changed it to true manually and it was happy after that.

[TerminalFault]

@itzg I just did a quick test. When you initially launch the container the EULA is correct per the config.

root@vmdkr01:/mnt/docker/data/mc_tnp5v2# docker-compose up
Creating network "mc_tnp5v2_default" with the default driver
Creating mc_tnp5v2 ... done
Attaching to mc_tnp5v2
mc_tnp5v2    | [init] Changing ownership of /data to 1000 ...
mc_tnp5v2    | [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 2 1000 1000 2 Aug 28 13:43 /data'
mc_tnp5v2    | [init] Resolved version given 1.18.2 into 1.18.2 and major version 1.18
mc_tnp5v2    | [init] Resolving type given FORGE
mc_tnp5v2    | [mc-image-helper] 13:45:38.541 INFO  : Downloading Forge installer 40.1.73 for Minecraft 1.18.2
mc_tnp5v2    | [mc-image-helper] 13:45:40.657 INFO  : Running Forge installer. This might take a while...
mc_tnp5v2    | [init] Checking if generic packs are up to date
mc_tnp5v2    | [init] Generic pack(s) are out of date. Re-applying...
mc_tnp5v2    | [init] Writing generic pack manifest ...

root@vmdkr01:/mnt/docker/data/mc_tnp5v2/data$ cat eula.txt
# Generated via Docker
# Sun 28 Aug 2022 01:45:34 PM EDT
eula=true

However once it gets to [init] Applying generic pack ... the EULA file is changed back to false.

root@vmdkr01:/mnt/docker/data/mc_tnp5v2/data$ cat eula.txt
eula=false

So it seems like the EULA is being written over when the modpack is being copied over. Double checking the modpack folder there is a EULA file inside the modpack. Deleting that from the zip seems to work also.

Since it's a separate issue I can split it off to it's own thread if it would help.

[itzg]

Well, that's annoying the Eula is bundled and overwriting.

Maybe that could be excluded by the unzip operation.

[Morr-valir]

Hello, to all, I have the same problem. For the modpack create above and biome. Despite GENERIC_PACK it does not work, I still have this error: "Modpack missing start script and unable to find Forge jar to generate one". Any solution? Even when downloading manually it doesn't work.

[itzg]

@Morr-valir when using GENERIC_PACK also be sure to change TYPE to "FORGE", etc.

[Morr-valir]

@itzg In my case the modpack comes from curseforge. Even with GENERIC_PACK, TYPE GENERIC_PACKTYPE 🧐. I may have an error elsewhere

[itzg]

@Morr-valir it doesn't matter if the modpack comes from CurseForge. When using GENERIC_PACK you must set TYPE to the specific server type along with VERSION.

For example, if it's a Forge modpack then set TYPE=FORGE and VERSION to the version of Forge that the modpack page describes.

[PreiMat]

I had the same Issue. My problem was that i das the wrong zip file. I tried to install Enigmatica6-1.5.1.zip on the server instead of Enigmatica6Server-1.5.1.zip. Maybe you have the same problem @Fruchtmolke

[itzg]

Well, that's annoying the Eula is bundled and overwriting.

Maybe that could be excluded by the unzip operation.

Thinking about this more, while talking with @TerminalFault , I'm thinking this could be handled by doing rm -f "${base_dir}/eula.txt" just after the extraction loop:

https://github.com/itzg/docker-minecraft-server/blob/8ab5542c82cd091837ef7c325382073ed9167fe1/scripts/start-setupModpack#L222-L225

That will then ensure that modpack supplied eula files are excluded.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open.

[PostWarTacos]

TYPE=FORGE and VERSION

Please fix the two docker-compose examples for Curseforge that seem directly contradict this.