Goobaroo

@stripeyhorse I pushed ATM 7 to the sky, by default it will install 1.1.2, but 1.1.1 is available too. It should show up in the Unraid Appstore by morning, it takes a while for new apps to go live.

Not really, that is not the design pattern of docker. Dockers are meant to be stand alone versions for a particular piece of software. Portable and re-usable regardless of the host system kind of like a VM image but much more compact. Docker containers are built on layers one of those layers in this case being the Java version being used. So you'd have to know ahead of time what version of java you needed. Then you'd need to know what the command is to start up the server for the particular mod pack you are running. None of them are the same, similar, but no the same. Except for maybe FTB, but even then it has its quirks and bugs in various releases that have to be worked around. Server packs aren't even always consistent between releases as to their startup parameters and config based on changes to Forge and the mods. All that being said, I can look into ATM7 to they sky. I am currently playing that pack.

Yes, done. Should be available now..

My FTB ocean block container has 1.15 and 1.15.1 that recently came out. You can see the versions on docker hub. https://hub.docker.com/repository/docker/goobaroo/ftboceanblock If you want to change the version you can change the settings for the container and add the version to the image. Right now it should simply be goobaroo/ftboceanblock this will grab the latest tag. But if you wanted 1.15.0, you could put goobaroo/ftboceanblock:1.15.0 and docker would download that version.

Sounds like you downloaded the wrong version of the mod for the version of the server that you are running. Make sure you're matching forge and Minecraft versions from the download page to go with the modpack you are trying to add mods to.

That information is all part of the container, you can view the layers on DockerHub. All the containers kick off by running /launch.sh, you can view the file in any running container.

If you want to add a mod separately, you'll need the version on both the server and your client. It sounds like you installed the client one already. If you browse into the `appdata/ftboceanblock` share, you can add the mod to the mods directory and it should get loaded on next start. Keep in mind an upgrade may reset the mods directory so that the modpack install is complete.

@Lyraik VaultHunters is fixed there are past versions there now too, plus the lates server version 1.13.9h. It was a combination of the server pack changing its install. Plus having a launch script "start.sh" that has a bug for setting JVM options. Both should be fixed.

I need to get some time to look at theses, but life has just been too hectic. Changes in the server releases sometimes require changes on my end to accommodate. No two servers install the same.

@Lyraik Seems like the install didn't happen. Can you delete everything in the vault hunters directory except the world directory and start the container up, it should reinstall. @BrainlessDude It has to be a different container. Each of the modpacks have their own issues to work through to get working. The core of the docker container is to download and install the version of the mod that is tagged as the version in the docker container. Swapping out files may work, but it's not 100%. I'm also playing ATM7 To the Skies, I'll look into it.

Hi @bsherman, you should be safe simply stopping the container.

@elokaynu Can you send me a long listing of your directory with the docker data? If you open a terminal on your server you can run this and send it back. Just trying to understand the state of things. ls -lah /mnt/user/appdata/skyfactoryone @RedRobo It is indeed an unraid thing. You should be able to open the file in a terminal on your server as you'll be logged in as root. When you browse to the appdata share in windows, the permissions are probably set to read-only.

@ToyRoBoHoBo & @elokaynu Both look like local permission issues. The correct ownership for the directory under /mnt/user/appdata should be nobody:users So for SevtechAges it is chown -R nobody:users /mnt/user/appdata/sevtechages SkyfactoryOne chown -R nobody:users /mnt/user/appdata/skyfactoryone

@Nio9345 Ownership of the files changed in the latest update. I suspect that prevented the install from properly cleaning up the last version. There was also an issue with the FTB installer that was generating bad paths. 1. On your unraid run: chown -R nobody:users /mnt/user/appdata/ftbskyfactory3 2. Delete the file /mnt/user/appdata/ftbskyfactory3/serverinstall_25_123 3. Start the server up again, it should get everything going.

Is ATM7 throwing errors, because I can confirm that it has the user gid/uid fix that I just put in SevTech.

I just pushed and updated version of SevTech. It has a change for the user in the container that runs the service. It should now match the nobody user. Seems that container got missed. See if choosing advanced in your docker and forcing an update solves it.

I can see a permission denied when trying to download and save the installer. Make sure the /mnt/user/appdata/sevtechages is writable to all.

Well, nothing really relies on BAT files. Those are just windows script files, to run a bunch of commands. Docker containers are linux based, so they use .sh files that are similar but run linux commands. In the case of Direwolf20, there was a bug with the FTB installer that generated unusable startup scripts, so I don't use run.sh or start.sh at all. The only thing you need to run is the correct java command. When the container is running, you can exec into it and take a look at the launch.sh script. But that script is immutable, meaning you can't change it as it is part of the docker container when it was built. I'm not familiar with Pterodactyl.

9.0.5 is the latest *server* version on CurseForge. I did see 9.0.6. There isn't always a corresponding server release with the client release.

9.0.5 is the latest version on CurseForge. If there was an update it may be client side only.

Check that the `/mnt/user/appdata/pixelmon/` directory exists and that it is owned by nobody and 777 permissions are set.

Can you send the log?

Order doesn't matter because those are now two completely independent Minecraft server instances. One is the base vanilla Minecraft and the other is ATM7. Good little overview of a docker container here: https://www.docker.com/resources/what-container/ That 12345 port number can be pretty much anything you want in the range of 1024-65535. Modded Minecraft servers are pretty resource heavy. So depending on how powerful your Unraid server is, it will determine how many different instances you can run simultaneously.

@hoss Docker containers are fully contained with everything they need to run the application that they are meant to run. I don't know what support the binhex Minecraft container has, but you don't need it to install my ATM7 container. Once ATM7 is installed on your unraid server, you have two options. By default the ATM7 should be configured to run in bridge network mode and you can set a different port number using the PORT config item in the ATM7 container settings. Do not change the port in the server.properties. The Host port will be used by clients for connecting to the server. You can see in the screenshot that docker is forwarding the network traffic from the bridge docker network to the unraid server IP and the configured port. You can change the networking in the ATM7 container to use your br0 network. This should allow the container to acquire it's own IP address from your local network and you can connect on that. You can even set a static IP as part of the container configuration.

@DarthLlama I'm looking into it, there is something funky happening with the FTB installer. I'm having similar issues on my end. I'll see if I can fix it.