Jump to content

Goobaroo

Members
  • Posts

    247
  • Joined

  • Last visited

5 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Goobaroo's Achievements

Contributor

Contributor (5/14)

56

Reputation

  1. Vault hunters wasn't updating due to some changes on their side. The latest version should be up now. 3.15.1.4
  2. @racingsquirrel DireWolf_20 1.21 should be up later tdoay. @FreakyBigFoot Are you referring to vanilla minecraft? I'm not producing containers for that, there are already excellent ones. @Dwarfboysim Modded minecraft requires both the server and client sides to match. I'm a fan of PrismLauncher for installing client side. The version of the modpack matters too.
  3. I'd recommend using something like Prism Launcher it can download the correct version of Java, Minecraft and all the mods in an easy searchable menu. It is what I use, and it works on Windows, Linux and MacOS.
  4. @Aildaan That last log line seems like the server started just fine. Are the kids machines running the same mod pack but client build? By default the container should be running on your Unraid server IP on port 25565.
  5. @TheHemogoblinLooks like the server zip failed to download completely. Delete it from the appdata directory and try again.
  6. @inactive-rower2548 Thanks for reporting. Should be fixed if you turn on advanced mode in the docker view and click the force update, it will pull the fixed 1.0.8 version of the container and resolve the issue. You'll also need to delete the server-1.0.8.zip file in /mnt/user/appdata/atm9sky for the re-install fix to work.
  7. You can't. But you can give yourself Operator privileges by adding your username to the container config under OPS. Any server commands can be run in game.
  8. @ReVRiN I took a look. It appears it needs a config change to load. There was an error message indicating such. If you edit the config/ferritecore-mixin.toml file and update populateNeighborTable = true the server starts. Problem with the server modpack itself. I can't validate right now, because Xbox Live is down, but your server should start.
  9. You should be able to add it to the mods folder, though it may have dependencies that you're missing. Keep in mind on upgrade, the mod folder is wiped clean and replaced by the one in the server install provided by the modpack owner.
  10. @AK90 There should be just an update button in your list of docker containers. Unless you have pinned the version of the container. The value in repository should be `goobaroo/atm9sky` which implies `latest` tag will be pulled. If you use a : after the name of the image you can specify a version. Like `goobaroo/atm9sky:latest` or `goobaroo/atm9sky:1.0.2` etc. These versions are listed on the docker hub page for the particular container. https://hub.docker.com/r/goobaroo/atm9sky What version of the server files is in your /mnt/user/appdata/atm9sky directory?
  11. @thomashp It should be fixed now. I re-published the 1.0.4 instance and it should be properly decompressing the zip. FYI: @ToxicCrow95
  12. @Brainwasher06 I don't modify the server installs, just wrap them in a docker container and automate the installation process. It would be way too much work to be patching individual releases and fixing other developer bugs. Changes will persist through restarts, just not upgrades. @Flosstradamus I'm not sure what is happening. The IP shouldn't matter, are you sharing a Minecraft account?
  13. @Mofarocker33 Hi, I'm not sure which of these logs correlate to what you are attempting to do. Moving appdata is usually on the array somewhere, and can be preferred to keep data on the cache. The issue you linked appears to be about swapping out the cache drive rather than the docker image. The docker.img file is used to store the images that you pull down for docker to use. From the looks of it there are some files missing in the Minecraft install. Try removing everything except the "world" directory in /mnt/user/appdata/allthemods9. Then start the docker container again and it should re-install with your world intact.
  14. @Jaime Alves Try the latest 0.2.58. I think they had incorrectly provided the wrong version of Forge in the 0.2.57 release.
  15. @michaelopolis You changed the Container Path to /appdata/. That needs to be reset back to /data/ The way a path works in Docker, is that the container path is where the Host Path will be mounted inside the container. Changing it to /appdata/ means that the scripts couldn't create any of the files on startup.
×
×
  • Create New...