-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Unable to resolve slug into ID (no matches)" #2968
Comments
Also getting, but very weird since foam hasnt been a dependency for atm since atm3 |
The error seems to stem from the recent push c87145a. The 'foamfix-for-minecraft' name isn't correct any longer so causes this error. |
Stay tuned, there's more I have to fix due to #2967 |
I removed my container and pulled the latest image, but I'm still receiving the same error. How do I go about spinning up my server container with the newest possible version? EDIT: FIXED I didn't remove the mod name from my exclude list. |
Since JEI is also included in globalExcludes, it seems that there might be an issue with it being deleted even though it is necessary for ATM9, preventing it from launching.
|
Even after purging my docker cache for images, with docker system prune -a, so I'm using using the lastest image published 3 hours ago, I still can't run ATM9 with the docker image. Everything unrolls at server startup and when the "Preparing spawn area" step comes, it stops at a random percent. |
@Shotman If you're making it that far then your issue is not directly related to originally reported one. What you may want to try is setting |
Describe the problem
"foamfix-for-minecraft"s slug has appeared to have changed to "foamfix-optimization-mod" which is forcing the container to exit. When I try to exclude foamfix-for-minecraft nothing changes. I attempted to create another container using AUTO_CURSEFORGE using ATM9 and got the same error with foamfix.
Container definition
Container logs
The text was updated successfully, but these errors were encountered: