ArKineX

@CmdrKeen, You da bomb! I just realized I had older folders of standalone Binhex Minecraft servers I was running before I switched over to MineOS...and I was putting the files there. Lolz.... After going into the "MineOS" folder I was able to drop the correct files there. Going to nuke the old binhex folders now. 😃

@Vinster411, Go to the Docker Container and edit it. Change the "Host port 2" setting. Make this the new range for your servers. Apply, and restart your docker. Then when you login to MineOS, go make sure the Minecraft server you want to change is stopped. Go to the server properties page of that server and change the "server port" of the server to a port in the range you designated. When you start the server back up and check the log output and see if the new port took affect and then you can test. Also make sure if you are hosting outside local you setup port forwarding on your router for the new Minecraft server ports you designated. I hope that helps.

Been awhile since I posted last, but I decided it was time to update my Minecraft servers to the latest PaperMC out now. Last version I have is for 1.17.1. I have seen a few others on this thread with this same issue...once on the latest version of the MineOS container, there is no longer an option for PaperMC in the profiles selection to choose from. @binhex, with the latest version of MineOS, was PaperMC removed on purpose due to some compatibility issue or something? I have tried manually downloading the latest PaperMC jar from their site, puttying into Unraid....putting the new jar in there...changing the permissions to 0777 and Users/Nobody, but nothing I do seems to make that work either. The new jar doesn't even show up on the "Change the running jar file to..." dropdown. My question is what do I do now? Am I stuck with 1.17.1? Since my servers are in PaperMC/bukkit format and would like to retain that, what do I use to bring my servers up to the latest? How can I force PaperMC manually if possible?. Any help would be appreciated!

@binhex can correct me here, but: 1) I believe the binhex-minecraft is for single server setups, but honestly I prefer MineOS as you have a GUI to manage your servers and you can have multiple servers running at once on MineOS. 2) Yes right now he is using Java 8, but I believe he will update his docker containers to 11 when 1.17 comes out. 3) That is a @binhex question. 😃

Hello everyone. I just wanted to confirm for everyone that after upgrading to Unraid 6.9.2, both of my PaperMC Minecraft servers are working with NO Java errors and the MineOS container can now run WITHOUT setting "Privileged" On. Big props to @binhex here for all the work he does! To avoid any issues I recommend that you: 1) Stop any Minecraft servers first 2) Do a backup of them (archive not restore point) 4) Upgrade to Unraid 6.9.2 and reboot. 5) If your container is set to startup on boot, login to MineOS and Stop the servers once more. 6) Perform the docker update to the latest 7) After the update go into the docker image and turn off "Privileged" You will still get the warning message on the Minecraft logs about the 1.17 update stuff, but I'm sure binhex will deal with that once 1.17 is released. Enjoy everyone!

Binhex: Thank you for all of the hard work you do! I just wanted to add a couple more notes: I'm running the image: binhex/arch-mineos-node:2cd410a44e4873ebb215048d51509be07bacd89a-01 Unraid 6.9.1 My java version is: I'm running papermc 1.16.5 for both of my Minecraft Servers. They both WORK on this image. But they ONLY work if the container is in "Privileged" mode. Otherwise I get the same issue as others above about "Operation not permitted". I'm not sure which MineOS image version these issues started at (I haven't tested).

Thanx for the shortcut to docker use the image you want via the method you show here! I upgraded to 6.9.1 as well. As per your suggestion, I'm still running the working "2cd410" image, but I turned "Privileged" off and restarted the container. It goes back to NOT working with it off. So I stopped and turned it back on...and it works. So it may work for some and may not for others. I'm not sure why that is. Might be a Unraid 6.9.1 thing specifically, but not sure.

After doing a lot of searching, I found this. I have the same issue as most of you with the Java errors when trying to start your Minecraft Server after the latest update to binhex's mineos. I also CAN CONFIRM that downgrading the image like user JKEJSER suggested WORKS!!! I should note that I am currently running Unraid Version 6.9.0 (I haven't updated to 6.9.1 yet. =/ ). Go here to grab that specific image: https://registry.hub.docker.com/r/binhex/arch-mineos-node/tags?page=1&ordering=last_updated&name=2cd 1) Just stop the current docker. 2) Open up the Server Terminal located at the top right of Unraid 3) Paste in the command to manually pull this image: docker pull binhex/arch-mineos-node:2cd410a44e4873ebb215048d51509be07bacd89a-01 4) The image will install with this specific Image ID. 5) Once done, make sure you open the container settings and turn on "Privileged" and click Done. 6) Start the container back up and log back into MineOS. Make note of the image ID after logging in at the top right under the login to confirm it loaded the correct image: 7) Start the server backup!