leptoid
-
Posts
7 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by leptoid
-
-
looks like "03 - InvokeAI" is broke again with this releaseIt is filling drive again. Going to find the new thing taking the space and map it out to the local drive
-
Updated version is working with invokeai.
Don't forget to download the models.
-
4 hours ago, Holaf said:
They changed the command name 😵
I will update that before tomorrow.
I also changed the default cache path to a path that's mapped on unraid to prevent filling docker.img
(it will no longer be necessary to add a path like I told you to do)Thanks buddy! I tried it with a different option (02) and that worked, thus confirming it was just not pulling the file or running it.
Downside to scripting... it only does exactly what it is told and doens't know when a dev changes something.
Thanks again for even taking the time to make, publish, and support everyone with getting it working.
AI is already paying off dividends. See below. -
Thanks! I tested that and it does prevent all the reserve docker space from filling. Item finishes compiling (I used UI option 03), then shuts down because it can't find invokeai.
- 1
-
On 11/19/2023 at 11:47 AM, anethema said:
EDIT: Pinning to the 1.5.1 tag made it stop happening so it is definitely an issue in the latest update.
Mine stopped working. invokeai just seems to do some reinstall loop then the container stops. Any idea? (I've made no other changes.
And here is the last log before the container stops:
This docker fills up the entire default UNRAID space reserved for docker... so you have to either make the default larger than 20Gb, or find a way to make it download the files and access them from local storage (without breaking their app). Mine is 17% full normally and goes to 100% when trying to install this. I suspect you have the same issue.
-
Same with a Geforce 3080Ti
[Support] Nodiaque - Gameserver docker
in Docker Containers
Posted
I was having issues, so I left the host up for 24 hours. Who knows if I can query it, but I found when I added it to Steam's Favorite servers, I was using the wrong port. I assumed it would connect to the game with the game port. WRONG. When I used the query port, 13657, it added and shows port 15636. If you're having trouble and everything else seems like it is working, try that. If it doesn't work, let it sit for the night and then try again.