Goobaroo

@TheHemogoblinLooks like the server zip failed to download completely. Delete it from the appdata directory and try again.

@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.

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.

@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.

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.

@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?

@thomashp It should be fixed now. I re-published the 1.0.4 instance and it should be properly decompressing the zip. FYI: @ToxicCrow95

@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?

@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.

@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.

@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.

Every template has a value named "Installed Location:" this has the path where the files are stored. Normally appdata is on the array under /mnt/user/appdata and a sub-directory is created there on start.

I'm not sure I understand the question as written. It sounds like your port forwarding isn't working possibly? What do you mean that your "server didn't communicate via internet"?

All The Mods 9 0.2.52 should be up

@PaddyZockt Hmm, there is not a server pack up for the 0.2.52 on curseforge, without one I can't publish one. Maybe it will show up a bit later.

@PaddyZockt 0.2.52 doesn't have a server release, it is client only. The 0.2.51 server should be compatible with it.

@Mofarocker33 It's still on the store, it just has spaces in the name. If you search by my name you'll see it too.

@Larunda Which container is that? That is only part of the log, I'd need the full log to see what went wrong earlier.

I can't be used to install a specific modpack. I publish dockers of certain modpacks for people to install.

What is in your ops.txt file? It may be called ops.txt.converted if it has already been processed by the game. It should be in the vaulthunters3 appdata directory.

@SimpleEnigma331 Oh, right. I was working on that. I'm, uhh... still working on it? I'll see if I can find some time later this week.

@skiiwee29 I'm just producing wrappers for installing the modded servers. I'm not going to manage issues related to the packs themselves. I'm sure they will get fixed on the FTB side. I monitor for new releases and push out updates as they go live. Update: They did fix it

@skiiwee29 seems to be a problem with the pack itself. The error I got was for the mod `embeddium-0.2.12+mc1.19.2.jar` Removing it got the server to start.

@obiwog I'm not sure what happened in your install. That error there looks like an incomplete jar file trying to be loaded. But I just upgraded mine from 0.2.14 to 0.2.34 and it worked fine. The only issue I saw was that the old `packmenu` directory wasn't being updated, so I've pushed a fixed 0.2.34 image.

Are you sad that there is a new version? There is a new docker with the latest 9-0.2.31. It was pushed 2 days ago. https://hub.docker.com/repository/docker/goobaroo/allthemods9/general