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

models.yaml can you do a test for me copy the attached models.yaml into your appdata/invokeai/userfiles/configs/ folder and see if the same error happens

added the Main docker for anyone wanting to migrate from prenodes to v3.0 beta, (this docker will be the default one for updates, i did it this way to not force everyone on prenodes to do the update) if you wish to do this migration, go to main post for instructions DO NOT do this if you dont want to do the migration to v3.0 beta yet

just a warning to others, going to 6.12.1 half of my dockers disappeared and had to be reinstalled, now I had to reinstalled all my dockers as they all disappeared after this update to 6.12.2, lucky the appdata and xml are all there.

Ok thats why, Yes all the legacy web server has been removed from main branch on get hub, however the nodes web server isnt fully ready for public use (still lots of changes happening), currently the front end needs to be yarn bulit on each start, runs on port 5173, the backend needs to be run separately and the whole user configuration file has changed. So You need to git clone -b prenodes, if you still want a working install, (or use the main dockerhub image in first post) I have docker image that loads nodes ui, but this will all change before the public release of invokeai v3.0 I can post when im back in the office what i had to do to get nodes ui to currently work if you wanted to see

Something has got messed up somewhere, you might need to delete all files but the userfiles folder, make sure your using the main image option in the first post and the my-invokeai.xml file is this updated on your flash drive from the first post and let it rebuild. This image is locked to the prenodes version of main, once node migtaion has been finalised and working, i will release an update. To that image

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. V2.3 did get some updates for xformers, you may need to delete the file /invokeai/venv/pyvenv.cfg and rerun the docker to fix the issue. 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.

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

If you can dont restart your docker, lastest updates will break it. Looking into a fix

I cant seem to replicate this error, is this the main or v2.3 docker? some things to try is delete the files in the invokeai/invokeai folder and let it repull from the repo and update the venv, if that doesn't work try this, in invokeai/venv folder delete the pyvenv.cfg file and rerun the docker

Thank you very much, but no need to tip me, the guys at invokeai are the ones doing all the hard work making there app, i just spent the time working out how to put it in a docker for unraid. I am happy it is working now. Just an fyi there is a major migration to nodes right now in the background of invokeai, so some updates might break the docker, so far it hasnt effected it, but I am keeping an eye on it