Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Vampire337

Members
  • Posts

    1
  • Joined

  • Last visited

Everything posted by Vampire337

  1. I am deploying the itzg/minecraft-server Docker container. This worked a few weeks ago, but something appears to be different today. I am using the following docker run command: docker run -d --name minecraft-java \ --restart unless-stopped \ -e TYPE=FORGE \ -e FORGEVERSION=36.1.24 \ -e SERVER_PORT=25565 \ -e EULA=TRUE \ -p 25565:25565 \ -v data:/data \ itzg/minecraft-server Without the FORGEVERSION parameter the downloaded Forge version is 36.1.0 (this issue affects 36.1.0 and 36.1.24 the same). Without the TYPE=FORGE parameter the container deploys as expected. Without the -d parameter I am able to see/capture the following output: [init] Setting white-list to 'false' in /data/server.properties [init] Adding server-name with 'Dedicated Server' in /data/server.properties [init] Setting server-port to '25565' in /data/server.properties [init] Setting motd to 'A Forge Minecraft Server powered by Docker' in /data/server.properties [init] Setting enable-rcon to 'true' in /data/server.properties [init] Setting rcon.password to 'minecraft' in /data/server.properties [init] Setting rcon.port to '25575' in /data/server.properties [init] Setting level-name to 'world' in /data/server.properties [init] Setting online-mode to 'true' in /data/server.properties [init] Checking for JSON files. [init] Setting initial memory to 3G and max to 3G [init] Starting the Minecraft server... 2021-05-31 22:44:38,145 main WARN Advanced terminal features are not available in this environment [22:44:38] [main/INFO] [cp.mo.mo.Launcher/MODLAUNCHER]: ModLauncher running: args [--gameDir, ., --launchTarget, fmlserver, --fml.forgeVersion, 36.1.0, --fml.mcpVersion, 20210115.111550, --fml.mcVersion, 1.16.5, --fml.forgeGroup, net.minecraftforge] [22:44:38] [main/INFO] [cp.mo.mo.Launcher/MODLAUNCHER]: ModLauncher 8.0.9+86+master.3cf110c starting: java version 16.0.1 by AdoptOpenJDK Exception in thread "main" java.lang.IllegalAccessError: class cpw.mods.modlauncher.SecureJarHandler (in unnamed module @0x50828c64) cannot access class sun.security.util.ManifestEntryVerifier (in module java.base) because module java.base does not export sun.security.util to unnamed module @0x50828c64 at cpw.mods.modlauncher.SecureJarHandler.lambda$static$1(SecureJarHandler.java:41) at cpw.mods.modlauncher.api.LamdbaExceptionUtils.uncheck(LamdbaExceptionUtils.java:95) at cpw.mods.modlauncher.SecureJarHandler.<clinit>(SecureJarHandler.java:41) at cpw.mods.modlauncher.Launcher.lambda$new$6(Launcher.java:55) at java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(Unknown Source) at cpw.mods.modlauncher.api.TypesafeMap.computeIfAbsent(TypesafeMap.java:52) at cpw.mods.modlauncher.api.TypesafeMap.computeIfAbsent(TypesafeMap.java:47) at cpw.mods.modlauncher.Environment.computePropertyIfAbsent(Environment.java:62) at cpw.mods.modlauncher.Launcher.<init>(Launcher.java:55) at cpw.mods.modlauncher.Launcher.main(Launcher.java:66) at net.minecraftforge.server.ServerMain$Runner.runLauncher(ServerMain.java:63) at net.minecraftforge.server.ServerMain$Runner.access$100(ServerMain.java:60) at net.minecraftforge.server.ServerMain.main(ServerMain.java:57) 2021-05-31T22:44:38.350Z WARN mc-server-runner sub-process failed {"exitCode": 1} 2021-05-31T22:44:38.350Z INFO mc-server-runner Done What is this trying to tell me, and is there more information I need to gather to troubleshoot effectively?
×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.