mickr777

Still active, the github repo got changed a while back, you can update that in you xml file (its not in the community apps if that where you were looking), all info in first post should be still up to date

Just did a fresh install and i couldnt get it to give that error, I repushed docker image to docker hub see if that helps

The empty folders should be made by the xml for them to be in the appdata eg mine is my-invokeai.xml (bit like an external symbolic link), then the script can use them like any other folder, but the data doesnt get wiped on docker image changes

I ended up having to have anything that I wanted in to the folders in appdata to be installed or ran in the start.sh script, if you want more info on that you can see all that in the main post under full manual install (I left comments in start.sh code to show what each section of it does), so in realty the docker image just has all the basic prerequisites to get the main install done with the start.sh. this was my first ever docker, so i just winged it and hoped for the best and it worked for unraid 😁

Updated onnxruntime and xformers

Updated to Support the change from yarn classic to pnpm

Yes but not easily, but my issue is I dont have a amd card to test it on

what docker image are you using? as models config should be here /home/invokeuser/userfiles/configs/models.yaml not where it is looking for it in /root/invokeai/configs/models.yaml with my docker image in first post

there was a issue where the needed models were not downloaded, to force a download, delete the file appdata/invokeai/venv/pyvenv.cfg only in unraid and rerun the docker, this will force the download of missing models.

fix for UI not loading I forced the docker to use the dev WebUI. if you are using the Dockerhub file: click the invokeai container and click update once updated right click the container and go edit change this line to the following next find webui port and click edit and change it to the following to access the webui now you have to use yourunraidip:5173. if you used the manual install: I have updated the files in main post you will need to rebuild your image and container with them. once built change the ports as the same as above also if you get startup aborted: there was a issue where the needed models were not downloaded, to force a download, delete the file /invokeai/venv/pyvenv.cfg and rerun the docker, this will force the download of missing models.

https://invoke-ai.github.io/InvokeAI/features/PROMPTS/#how-dynamic-prompts-work That might help If you have discord you should join the invokeai server https://discord.gg/ZmtBAhwWhy Also if it using the gpu you should see it on start in your docker logs

If you on the manual setup Should only have to delete and rebuild the container with the new files, if your on the docker hub images remove container delete image, then add docker back but change the repo to mickr777/invokeai_unraid_main and start it should migrate everything for you 🤞(minus your outputs folder it need to be backup, as it will not show in new version)

found the issue (I think) grab the updated start.sh file info from main post and delete container (but remove delete image tick box) recreate the container, as the main post or used the Simplified Install for main, as I pushed an update to it (use either way but make sure to delete the appdata/invokeai/venv/pyvenv.cfg and if you have it appdata/invokeai/userfiles/invokeai.init files)

looks like they changed the way the invokeai-configure script works I will have to do some testing

there shouldn't be any config folder in the invokeai folder but you can add the folder and models.yaml there and see if that helps