Marshin

here is the stack from my docker version: "2" services: minecraft-server: image: itzg/minecraft-server:java17 container_name: MC118 network_mode: host environment: - PUID=998 - PGID=100 - EULA=TRUE - VERSION=LATEST - MEMORY=8G - ANNOUNCE_PLAYER_ACHIEVEMENTS=true - ALLOW_NETHER=true - GENERATE_STRUCTURES=true - PVP=false - TYPE=FORGE ports: - 25565:25565 volumes: - /srv/dev-disk-by-label-data/MC118:/data restart: unless-stopped

Being is that I am starting the server via a stack in docker I don't know that I have any control as to how the .sh file is ran. I know I am not as experienced as the majority of the people on this forum. so if someone want to explain to me how I can change how file get ran inside the docker stack I will gladly try it. Please let me know if you need me to provide more info.

I'm using Docker to run a server, how ever when I try to add Forge it fails to start. at this point this is a vanilla server and only trying to add forge. my log when trying to start the latest Forge version Actions [init] Running as uid=1000 gid=1000 with /data as 'drwxrwsrwx 8 1000 1000 4096 Jan 2 20:57 /data' [init] Resolved version given LATEST into 1.18.1 [init] Resolving type given FORGE [init] Checking Forge version information. [init] server.properties already created, skipping [init] Updating ops [init] Checking for JSON files. [init] Setting initial memory to 8G and max to 8G [init] Starting the Minecraft server... Error: Invalid or corrupt jarfile /data/run.sh 2022-01-04T01:33:23.433Z WARN mc-server-runner sub-process failed {"exitCode": 1} 2022-01-04T01:33:23.433Z INFO mc-server-runner Done here is the installer log https://github.com/Marshin386/forge-1.18.1-39.0.10/blob/d8e66c66a8ce37c3f3d7439739638692fdde9eb5/forge-1.18.1-39.0.10-installer.jar.log