-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forge installer exception: java.util.zip.ZipException: zip END header not found #2283
Comments
I can't recreate the problem and besides, that's the forge installer failing. I'm not sure how I can address that. Also, you seem to have a very old image if running latest reports
Should be reporting Java 17.0.7:
|
Sorry, I had been trying various versions of the image as a troubleshooting measure, the result is the same with all image versions.
|
That error means there's a corrupted zip/jar file. Again, it's failing during the forge installer and I can't recreate the issue. Try a fresh system or report an issue with forge. |
For whatever reason, server-<version>.jar was never downloading completely. I checked and the version downloaded automatically was roughly 8MB. Downloading the file myself and replacing it with the full 45MB file fixed the problem. I wish I knew what the root problem was since there's presumably no meaningful difference between our environments, we should be downloading from the same place and I was working with an empty /data directory. For my purposes the issue is resolved with a work-around of manually replacing the corrupted jar file. |
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. |
Just reporting, i'm facing the same error today with ATM9 deployment. Fail at the same spot. I also had issue with the PT20S timeout, adding the variable suggested in another thread to my docker-compose didn't have impact on the timeout, it still timed out at 120000ms. Thanks for this thread by the way, that was the only clue I could find about this problem. [mc-image-helper] 18:59:09.657 INFO : Requested CurseForge modpack All the Mods 9-0.2.43 is already installed for All the Mods 9 - ATM9 Running this command after docker compose run successfully. docker run -it -e EULA=TRUE -e TYPE=FORGE docker.io/itzg/minecraft-server:latest |
@ocontant How did you find what .jar file was corrupted? Also running into this issue with ATM-9.
|
Describe the problem
When instantiating a new pod for Forge without mods (any version it seems), I get the output below and the container fails to start. I've tried multiple versions of Forge and minecraft all with the same result. I switched the type to PAPER with latest as version and startup was successful.
Container definition
Container logs
The text was updated successfully, but these errors were encountered: