-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
nixosModule: models.yaml not found exception #72
Comments
We need VM Tests. But I do not currently have the time to work on that. Try the release of nixified-ai instead of the latest master. |
Since release doesn't currently build, this is not an valid option for me currently:
The original issue I'm facing: |
@MayNiklas As noted in the release notes:
This is because the upstream project does not have an automated or stable way of moving from one version or another, this happens to people using InvokeAI normally too. So just remove your state in |
I did this. This system never had invokeai installed before |
What do you mean the release doesn't build? |
Just confirmed, the release does build. Use |
Puh, I can confirm: |
For some reason, it builds a different package when being installed through my flake repo. I'm very confused and will investigate it once I find some time. |
When trying to use that, I still get an error:
|
Try using invokeai-model-install --yes --default-only --config_file <invoke-folder>}/config_custom.yaml before starting the app itself. |
A few things to note:
Doing this causes upstream program (InvokeAI) to break in mysterious ways due to bad argument handling logic. Stop passing it.
|
Oh okay! Thanks. I just watched your video where you passed in that config, so I thought I had to do that |
@eikooc yeah unfortunately InvokeAI is buggy, backwards incompatible, complex and unstable, just get rid of the state when you can and you'll be alright. If we fetched the models with Nix we could obsolete 99.9% of what |
I got the v2 branch to build!
-> the initial configuration of the NixOS module does not seem to work. If wanted, I can try to fix the issue by creating a initial startup script within the module. |
@MayNiklas If you can PR a fix then go ahead, otherwise use |
In theory, even having a test that checks if the service starts successfully would be very helpful. |
CUDA is another problem, we can define a VM Test that checks the program works with CPU. And I do have an old machine and nvidia GPU I can set up in CI. Doing this in CI, and passing through the GPU will not be a problem. |
I've tried to install
invokeai-nvidia
on my server (I'm using flakes):The service always fails on startup:
I've tried deleting
/var/lib/invokeai/
- changed nothing.Is the NixOS module currently meant to be working?
Are there any known workarounds for the issue I'm facing?
The text was updated successfully, but these errors were encountered: