Jump to content

ShadowUnraidLegends

Members
 View Profile  See their activity

  • Posts

    4

  • Joined

  • Last visited

 Content Type 

Posts posted by ShadowUnraidLegends

    [Guide] InvokeAI: A Stable Diffusion Toolkit - Docker

    in Docker Containers

    Posted · Edited by ShadowUnraidLegends

    22 hours ago, mickr777 said:

    What image are you on the main or v2.3, also what errors are showing for you?

     

    Currently while the migration to nodes i locked the main image to the prenodes tag, so it shouldnt be getting any updates at the moment till the migration has finished, so anything they do should not effect it.

     

    As for the current main branch on git hub I have a working image for it but lots still dont work, the ui needs to be used in dev mode and  things change so much with every update, I didnt think anyone on main wants that yet.

     

    I am on the main branch, obviously I get a few hiccups here and there but their GitHub is fairly responsive at fixing stuff, usually I have been relatively stable. I'm now getting this in my log with an inability to load into webui:
      

    `[21-05-2023 21:18:02]::[InvokeAI]::INFO --> Patchmatch initialized
[21-05-2023 21:18:03]::[InvokeAI]::INFO --> InvokeAI, version 3.0.0+a0
[21-05-2023 21:18:03]::[InvokeAI]::INFO --> InvokeAI runtime directory is "/home/invokeuser/userfiles"
[21-05-2023 21:18:03]::[InvokeAI]::INFO --> GFPGAN Initialized
[21-05-2023 21:18:03]::[InvokeAI]::INFO --> CodeFormer Initialized
[21-05-2023 21:18:03]::[InvokeAI]::INFO --> Face restoration initialized
[21-05-2023 21:19:17]::[InvokeAI]::INFO --> Patchmatch initialized
[21-05-2023 21:19:17]::[InvokeAI]::INFO --> InvokeAI, version 3.0.0+a0
[21-05-2023 21:19:17]::[InvokeAI]::INFO --> InvokeAI runtime directory is "/home/invokeuser/userfiles"
[21-05-2023 21:19:17]::[InvokeAI]::INFO --> GFPGAN Initialized
[21-05-2023 21:19:17]::[InvokeAI]::INFO --> CodeFormer Initialized
[21-05-2023 21:19:17]::[InvokeAI]::INFO --> Face restoration initialized
[21-05-2023 21:19:48]::[InvokeAI]::INFO --> Patchmatch initialized
[21-05-2023 21:19:48]::[InvokeAI]::INFO --> InvokeAI, version 3.0.0+a0
[21-05-2023 21:19:48]::[InvokeAI]::INFO --> InvokeAI runtime directory is "/home/invokeuser/userfiles"
[21-05-2023 21:19:48]::[InvokeAI]::INFO --> GFPGAN Initialized
[21-05-2023 21:19:48]::[InvokeAI]::INFO --> CodeFormer Initialized
[21-05-2023 21:19:48]::[InvokeAI]::INFO --> Face restoration initialized
From https://github.com/invoke-ai/InvokeAI
ff0e79f..650d69e main -> origin/main
02d2cbc..23abaae feat/images-service -> origin/feat/images-service
[22-05-2023 07:45:17]::[InvokeAI]::INFO --> Patchmatch initialized
[22-05-2023 07:45:17]::[InvokeAI]::INFO --> InvokeAI, version 3.0.0+a0
[22-05-2023 07:45:17]::[InvokeAI]::INFO --> InvokeAI runtime directory is "/home/invokeuser/userfiles"
[22-05-2023 07:45:17]::[InvokeAI]::INFO --> GFPGAN Initialized
[22-05-2023 07:45:17]::[InvokeAI]::INFO --> CodeFormer Initialized
[22-05-2023 07:45:17]::[InvokeAI]::INFO --> Face restoration initialized
[22-05-2023 07:55:55]::[InvokeAI]::INFO --> Patchmatch initialized
[22-05-2023 07:55:55]::[InvokeAI]::INFO --> InvokeAI, version 3.0.0+a0
[22-05-2023 07:55:55]::[InvokeAI]::INFO --> InvokeAI runtime directory is "/home/invokeuser/userfiles"
[22-05-2023 07:55:55]::[InvokeAI]::INFO --> GFPGAN Initialized
[22-05-2023 07:55:55]::[InvokeAI]::INFO --> CodeFormer Initialized
[22-05-2023 07:55:55]::[InvokeAI]::INFO --> Face restoration initialized
From https://github.com/invoke-ai/InvokeAI
0ce628b..fab5df9 v2.3 -> origin/v2.3
[22-05-2023 07:57:49]::[InvokeAI]::INFO --> Patchmatch initialized
[22-05-2023 07:57:49]::[InvokeAI]::INFO --> InvokeAI, version 3.0.0+a0
[22-05-2023 07:57:49]::[InvokeAI]::INFO --> InvokeAI runtime directory is "/home/invokeuser/userfiles"
[22-05-2023 07:57:49]::[InvokeAI]::INFO --> GFPGAN Initialized
[22-05-2023 07:57:49]::[InvokeAI]::INFO --> CodeFormer Initialized
[22-05-2023 07:57:49]::[InvokeAI]::INFO --> Face restoration initialized
Downloading sd-inpainting-1.5:
Downloading stable-diffusion-2.1:
** models.yaml exists. Renaming to models.yaml.orig
Successfully created new configuration file /home/invokeuser/userfiles/configs/models.yaml

** INVOKEAI INSTALLATION SUCCESSFUL **
If you installed manually from source or with 'pip install': activate the virtual environment
then run one of the following commands to start InvokeAI.

Web UI:
invokeai-web

Command-line client:
invokeai

If you installed using an installation script, run:
/home/invokeuser/userfiles/invoke.sh

Add the '--help' argument to see all of the command-line switches available for use.

Loading InvokeAI WebUI.....
invoke> Checking if The Git Repo Has Changed....
Local Files Are Up to Date
Loading InvokeAI WebUI.....
invoke> Checking if The Git Repo Has Changed....
Local Files Are Up to Date
Loading InvokeAI WebUI.....
invoke> Checking if The Git Repo Has Changed....
Updates Found, Updating the local Files....
Updating ff0e79f..650d69e
Fast-forward
invokeai/frontend/web/src/app/components/InvokeAIUI.tsx | 11 +++++++++--
.../src/features/gallery/components/CurrentImageButtons.tsx | 8 +++++++-
.../web/src/features/gallery/components/HoverableImage.tsx | 8 +++++++-
invokeai/frontend/web/src/features/gallery/store/actions.ts | 4 ++++
4 files changed, 27 insertions(+), 4 deletions(-)
Loading InvokeAI WebUI.....
invoke> Checking if The Git Repo Has Changed....
Local Files Are Up to Date
Loading InvokeAI WebUI.....
invoke> Checking if The Git Repo Has Changed....
Local Files Are Up to Date
Loading InvokeAI WebUI.....
invoke> `



    Seems like it's getting stuck on VAEs or install again, and I was under the impression that something in the actual main branch changed, and their perspective was that possibly we're loading onto legacy servers which they shutdown around the same time as when this stopped working for me. (few days ago as I am understanding).


    Sometimes I am out of my league talking about this stuff, so sorry if I am using any terms incorrectly/confusingly!

    [Guide] InvokeAI: A Stable Diffusion Toolkit - Docker

    in Docker Containers

    Posted

    On 5/3/2023 at 10:51 PM, mickr777 said:

     

    yes this is the breaking issue, just uploaded a quick fix to docker hub, locked the current main branch to the pre-nodes tag till main migration to nodes is done.

     

    however if there is files under /invokeai/invokeai/ they will need to be deleted before starting the docker so it can pull the pre-nodes tag.

     

    Side note ignore these errors for now since pre-nodes is a tag not a branch:

    fatal: HEAD does not point to a branch
    fatal: HEAD does not point to a branch
    start.sh: line 38: [: fdad62e88b77478ef7016e447aeed6a221149f6b: unary operator expected
    start.sh: line 40: [: fdad62e88b77478ef7016e447aeed6a221149f6b: unary operator expected

    Am I understanding right that this is using the legacy servers? They've made an update and removed them, so I think things need to be changed as my docker doesn't work anymore.

    quote from github:

    Quote

    The legacy web server has been removed. You'll need to launch the new web server with invokeai-web (not invokeai --web) from the command line:

    source ~/invokeai/.venv/bin/activate # linux C:\YourUserName\invokeai\.venv\Scripts\activate # windows invokeai-web

    Note that the web script currently requires you to be in the root directory of the repo.

    We've basically thrown all the pieces up in the air and are trying to put them back together again, so various bits of the install and configure process are not working.



    Unless I am wrong and I've just messed up my own Invoke! Cheers.

    [Guide] InvokeAI: A Stable Diffusion Toolkit - Docker

    in Docker Containers

    Posted

    6 hours ago, mickr777 said:

    Sounds like the ptyhon venv may not have been setup correctly during the first run, if you have Dynamix File Manager plugin installed, in unraid go to it then go to the folder cache, appdata, invokeai then venv and delete the pyvenv.cfg file and rerun the docker.

     

    The file Could also be deleted via the unriad terminal if you dont have that plugin


    Wow. Just wow. Maybe it's the espresso, but you have no idea how overwhelmingly grateful I am to you right now. 

    All week I've back and forth'd solving issue after issue, finally reaching this final issue that no help was solving. Here comes you, who did all the hard work creating this stuff, AND you are so diligent you - within 12 hours - see my comment and instantly come to the rescue and solve it with 2 sentences?


    Please tell me you have a BuyMeACoffee or some way to donate you a little tip as a thanks.. been having a hard time lately w/ lots of stuff and having this small thing finally work after a lot of hours really is a silver lining to my life.

    • Like 1

    [Guide] InvokeAI: A Stable Diffusion Toolkit - Docker

    in Docker Containers

    Posted

    Firstly - thanks so much for all the hard work making this, and making a super guide. 

    I've run into a problem while installing this all, and as a fairly amateur UnRaid user could use anyones insights.

    I've seemingly got InvokeAI installed, I have the NVIDIA drivers installed (RTX 2070), but get two errors I don't get:

    1) invokeai: command not found, context:

    Quote

    start.sh: line 61: invokeai: command not found

    start.sh: line 61: invokeai: command not found

    Checking if The Git Repo Has Changed....

    Local Files Are Up to Date

    Loading InvokeAI WebUI.....

    Checking if The Git Repo Has Changed....

    Local Files Are Up to Date

    Loading InvokeAI WebUI.....

    ** Press ANY KEY to close this window **

     

     

    2) Exited (127)

    That shows under my uptime, as it instantly just goes to 'stopped' when I try to start invokeai docker.

     

     

    Sorry if I am not sharing enough info, I used option #1 for my install. On Version: 6.11.5 of UnRaid.

     

     

     

×
×
  • Create New...