[[Support] binhex - MineOS-node]

Yep! Yeah, I tried with just running it as privileged and that did not work for me. Using the XML change AND running as privileged is currently working (definitely agree that having it be privileged is a terrible, but temporary fix!)

[[Support] binhex - MineOS-node]

Like others have posted, I also ran into the same issues with java in the latest docker image (binhex/arch-mineos-node:5670b46c4f22e806ce5819a7f86042df4b4ecc23-04). I also tried setting the container to have privileged mode but still had the same issue as well (see spoiler).

 

Spoiler

[13:42:58] ain/FATAL]: Failed to start the minecraft server
java.lang.RuntimeException: java.nio.file.FileSystemException: .: Operation not permitted
at net.minecraft.server.v1_16_R3.Convertable.<init>(Convertable.java:42) ~[patched_1.16.5.jar:git-Paper-553]
at net.minecraft.server.v1_16_R3.Convertable.a(Convertable.java:50) ~[patched_1.16.5.jar:git-Paper-553]
at net.minecraft.server.v1_16_R3.Main.main(Main.java:112) ~[patched_1.16.5.jar:git-Paper-553]
at org.bukkit.craftbukkit.Main.main(Main.java:276) ~[patched_1.16.5.jar:git-Paper-553]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_282]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_282]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_282]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_282]
at io.papermc.paperclip.Paperclip.main(Paperclip.java:58) ~[paper-1.16.5-553.jar:?]
Caused by: java.nio.file.FileSystemException: .: Operation not permitted
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) ~[?:1.8.0_282]
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) ~[?:1.8.0_282]
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) ~[?:1.8.0_282]
at sun.nio.fs.UnixPath.toRealPath(UnixPath.java:837) ~[?:1.8.0_282]
at net.minecraft.server.v1_16_R3.Convertable.<init>(Convertable.java:40) ~[patched_1.16.5.jar:git-Paper-553]
... 8 more

 

 

After reading through the issues referenced in itzg/docker-minecraft-server issue 795, I found that the developer ended up currently resolving the issues by adding the :Z flag to the volume mount for docker. Changing the mount flag to be rw,Z

with the container in privileged mode fixed the issue. Why? I have no idea, but it works reliably for now! I think the Z mount flag is related to something with AppArmor, so that may be related within parts of the image?

 

To change the mount flag, you need to edit the configuration file generated on the flash storage device for Unraid (the webUI does not support these additional docker flags). I found help from this forum post, but basically just edit /boot/config/plugins/dockerMan/templates-user/my-binhex-mineos-node.xml and change the Mode XML value within the Volume section to be rw,Z instead of rw.

It should look something like this:

 

Spoiler

  <Data>
    <Volume>
      <HostDir>/mnt/user/appdata/binhex-mineos-node</HostDir>
      <ContainerDir>/config</ContainerDir>
      <Mode>rw,Z</Mode>
    </Volume>
  </Data>

 

Hopefully this helps for troubleshooting the root issue for the image! Setting privileged mode to make this work shouldn't really be necessary, since the container will be less secure than normal with greater permissions to the host OS.