Goobaroo

@Siggz Probably because you're still pointing to the siggz tag I made for you that is the previous version. Just remove the tag, or replace it with latest and it will get the latest build. goobaroo/ftbdirewolf20_118:siggz -> goobaroo/ftbdirewolf20_118

It's beginning to sound like you may have some bad RAM and this container is hitting it with your current running config.

Vault hunter 0.0.2 was a client side update only, there was no server for that release. They don't always release a new server for each version.

When docker stops a container it does send a shutdown signal to the process. After 10 seconds it will send a kill. I can take a look at improving that within docker, but it shouldn’t matter that much. Are you running into an issue? You can stop the server in game if you have added yourself to the OPS variable in the server config in Unraid. Then just run /stop in game.

@DarthLlama TLDR; Changing the server properties port will break the container and is not necessary to access it on another port. See here for a longer explanation:

@sportsziggy Thanks. Did need some work but should be available as soon as unraid syncs up with my list of apps. Edit: Vault Hunters 3rd Edition 1.18.2 is available.

@sportsziggy I don't see a vault hunters release on curseforge and that is where the server pack gets installed from. When there is an actual release I can update it.

@CRDark That wasn't quite ready for release. But I have fixed it up properly now, so it should work if you force an update or remove and completely re-install. You'll have to wipe out the files in the rlcraft appdata directory in order for it to install properly. To answer your other question about a guide, I don't have one. Fundamentally the containers are an install/update script. That downloads the version of the server files needed for a particular mod pack and exposes the environment variables from the unraid application config to allow it all to run. Each server has its particular version of Java as the parent container that runs the server. For some packs it is easy, there is an install script. For others, like RLCraft no help is given other than some server requirements and I had to write an installer to take care of it.

@Marik900 That's a problem with the pack, not the container. But I can suggest some solutions. You can delete the serverinstall_100_2295 file and the mods directory and restart the container. That should redo the install, probably fix the problem.

@ChongZhiJie You don't need to change the server.propeties at all. That port layer is inside docker, changing it will only break the networking for the container because it is expecting the default port of 25565. To use a different port just change the PORT value in the docker config, and use the bridge network. It will then map the port you defined to your unraid server IP and you can port forward that publicly if you like. Here are two servers running on my server. That column on the right shows the mapping of the port and IP inside the docker network on 172.17.0.0 to the IP of my unraid server and the mapped port. Or alternatively you can use br0 network and give each docker container their own IP on your internal network and port forward to that instead. But changing the server.properties will only break it.

@TheNakedFlame Each docker is specific to a version. So yes, there will be an update, I'll keep an eye out for it. If there are any issues, I'll try and address them. I believe that Vault Hunters is going 2.0 with the 1.18 update. It will still be the same container name it will just get updated.

@Raiever I think the install got interrupted the first run. Deleting the serverinstall_95_2291 file, that will re-start the install process.

@Raiever What is in the appdata directory for the pack. It looks like the forge jar is missing entirely. @eebs Thanks, I've fixed and republished the container for the latest version. Seems they changed their server pack.

@Siggz I found this bug: JDK-8292171, someone having a similar crash, though it is Java 11 and this one is Java 17. Do you want to test a custom build? I upgraded the container to use Java 18.0.2. It works on my machine, I'm wondering if it will be okay on yours. It is version 1.10.1 of the modpack. Just edit your install and change the Repository from goobaroo/ftbdirewolf20_118 to goobaroo/ftbdirewolf20_118:siggz That will pull down the Java 18 image instead.

@eebs Done. Thanks for raising it.

@Siggz Can you attach the hs_err_pid160.log file? It should be in appdata/ftbdirewolf20_118 What version of Unraid are you using?

@Gr8Lightning & @DarthLlama I found that the forge installer is left behind and getting sucked into your startup command. I can make sure installers get cleaned up, but if you manually delete the forge-*-installer.jar files in your install directories, everything will work. java -server -XX:+UseG1GC -XX:+UnlockExperimentalVMOptions -Dfml.queryResult=confirm -Dlog4j.configurationFile=log4j2_112-116.xml -Xms6144m -Xmx9182m -jar forge-1.16.5-36.2.33-installer.jar forge-1.16.5-36.2.33.jar nogui

@bbilko Java is crashing on the first attempt to start up. Do you have enough free system memory? It is allocating 6GB to the docker container. What is in the hs_err_pid14.log? What CPU is in your unraid server? # A fatal error has been detected by the Java Runtime Environment: # # SIGILL (0x4) at pc=0x00001499453dfe04, pid=14, tid=15 # # JRE version: OpenJDK Runtime Environment (17.0.2+8) (build 17.0.2+8-86) # Java VM: OpenJDK 64-Bit Server VM (17.0.2+8-86, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64) # Problematic frame: # J 1823 c2 java.util.stream.StreamSupport.stream(Ljava/util/Spliterator;Z)Ljava/util/stream/Stream; [email protected] (19 bytes) @ 0x00001499453dfe04 [0x00001499453dfd20+0x00000000000000e4] # # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /data/hs_err_pid14.log

@A_MrNew versions of the containers get updated fairly frequently. If you're looking at the settings of any docker container, if there is no version defined then it is defaulting to the `latest` tag which should float to the newest version. For example: goobaroo/stoneblock3 is equal to goobaroo/stoneblock3:latest where goobaroo/stoneblock3:1.0.0 specifies a version. You'll see in your docker list an update button when there is a new version, this is a function of unraid. Which container are you asking about? Edit: If you mean automatically update dockers when a newer version is out, you can do that with the CA Auto Update Applications plugin. Their support thread is here

I'm not entirely clear what you're trying to say here. The File name changes between server releases. The URI is coming from a CDN so the path changes with each release and pack as well. As a whole the launch.sh is generated in an automated CI/CD stack. While they are templated, the information about where and what to download do change. Occasionally the launch.sh needs to be updated to combat quirks in the server install or bugs introduced in order to successfully complete.

Docker containers are meant to be fixed stand alone versions of a particular piece of software. They are highly portable as they include everything that is needed to run an application. In the case of these servers, they start with a Java container, using the appropriate version 8, 11, 17 what ever. Then in my case a launch script is written to download the server for what ever mod pack the container is configured to install. It then runs the initial setup and installs it. I have to tweak the install process or write it in the case of ATM, as all they give is a readme with the install instructions for setting up a server. But for all the versions I publish it will always queue the install off of wether it finds the ZIP file with the server install in its appdata directory, if it is there, it assumes it is already installed. When it upgrades it removes the previous version, downloads the new version and does an upgrade.

It seems like the install was partially completed. Either because it was interrupted or you ran out of space. The install saves its files to `/mnt/user/appdata/allthemods8`. If you delete the `Server-Files-0.1.8.zip` file in that directory and start the container, it will re-install. Give that a try first. The first startup takes a while as it is installing forge and patching everything. The install takes about a 1 Gb of space.

@salty Well I have good news for you, I just published an ATM8 server container. You can simply install and use that one.

Which docker are you trying to install? Can you also attach the entire log?

@CiscoCoreX Yes. Should be there now in the apps store.