Geoff Bourne

> But why would 1.16 and 1.17 all work perfectly fine, but 1.8 (or latest) fails? If it was a filesystem issue, wouldn't that affect any version? I'm not sure....

Thanks, that is a good suggestion. My concern is that garbage collection will compact the JVM's heap memory, but I don't believe it will release any of that heap allocation...

Good research. So it might turn out that users adding those options for Java 8 containers and relying on the default G1 for Java 17 etc might the best that...

Thanks for the info and links.

Interesting. So their release names convey the applicable Minecraft version. Looks like Catserver support will need to be completely re-written then. Contributions are welcome.

You'll need to use an image tagged for Java 8 rather than the default of Java 17 for Forge less than 1.18: https://docker-minecraft-server.readthedocs.io/en/latest/versions/java/

Please provide the new logs for Forge 1.20.4. You will need to use Java 17 for that.

Make sure you have the latest image by running ``` docker compose pull ``` That sounds like an issue with Forge 1.20.4 that was recently fixed in the image.

That'll be a TrueNAS problem or whoever maintains that chart. That version is quite old and missing 44 changes at this point https://github.com/itzg/docker-minecraft-server/releases/tag/2023.11.1 Please contact the appropriate maintainer there.

> It's unlikely to work with 44 updates not posted on Truecharts. Agreed. Specifically, they need to pick up this change from image tag 2023.12.2 and newer https://github.com/itzg/docker-minecraft-server/commit/6363949bda8b9cc1cfb35d93fc3dd61c0b089e43