Holaf

Members
  • Posts

    77
  • Joined

  • Last visited

1 Follower

About Holaf

  • Birthday 12/19/1973

Converted

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Holaf's Achievements

Rookie

Rookie (2/14)

32

Reputation

  1. I think you should remove (after doing a backup) the /user/mnt/appdata/stable-diffusion/70-kohya/kohya_ss folder. I don't know what he says that you modified two files, but that's why it can't update.
  2. I was referring to this part of the log : Remote branch is ahead. Wiping venv for clean packages install Updating 6162193..5bbb4fc ------------------------------------- Cleaning venv Done! ------------------------------------- In the last test version I force the update of local files, and I removed the systematic clean when there is an update. This time I hope it will be ok
  3. ohhh ! That's why I thought it was ok 😵‍💫 A clean venv is launched every time there is an update of the repository. I will remove that and let only the "manual" cleaning.
  4. @Araso in the last test version : -corrected a bug where the default output folder for auto111 wasn't linked to the common folder -corrected a bug where the virtual env for koyha was deleted at every launch -renamed the files used for clen env and reset rights (to get rid of spaces) hope this time everything is right
  5. Thanks a lot for your feedback, i'll try to fix those two things as soon as possible. And you're rignt for the filenames, i'll change it too
  6. @Araso If you want to try the test version, I think I fixed Koyha (not 100% sure since I don't use it) Perhaps you'll have to set up acceleration in the parameters (at least to tell which GPU to use) For your problem of permissions I did what you suggested. There is now two files at the root of the config folder : 'Delete this file to clean virtual env and dependencies at next launch' 'Delete this file to reset access rights at next launch' I think it's pretty clear, and please tell me if it solves your issue.
  7. Sorry, I was a little busy the last days, i'll try to fix as much things as possible this weekend
  8. I'll try to make coresponding changes this weekend, i'll keep you updated
  9. with a clean install on the last version I have no errors 12/03/2024 11:07:02 Building wheels for collected packages: insightface 12/03/2024 11:07:02 Building wheel for insightface (pyproject.toml): started 12/03/2024 11:07:07 Building wheel for insightface (pyproject.toml): finished with status 'done' 12/03/2024 11:07:07 Created wheel for insightface: filename=insightface-0.7.3-cp311-cp311-linux_x86_64.whl size=873701 sha256=87ee8a0b7c162192252daa84f7eec0b04cfeef8f771a2fb2bb1bd90a1f41857d 12/03/2024 11:07:07 Stored in directory: /config/temp/pip/wheels/27/d8/22/f52d858d16cd06e7b2e6aad34a1777dcfaf000be833bbf8146 12/03/2024 11:07:07 Successfully built insightface I changed the packages I install before running forge/auto11 : pip install --upgrade pip pip install coloredlogs flatbuffers numpy packaging protobuf==3.20.3 sympy pip install packaging pip install onnxruntime-gpu --extra-index-url https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-cuda-12/pypi/simple/ pip install insightface pip install basicsr pip install torch==2.2.0 torchvision==0.17.0 torchaudio==2.2.0 --index-url https://download.pytorch.org/whl/cu121 pip install xformers --index-url https://download.pytorch.org/whl/cu121 I see that you have this error : error: command '/config/02-sd-webui/conda-env/bin/gcc' failed: Permission denied perhaps the virtual env didn't rebuild as expected (but I dont know why). perhaps you should do a clean install by removing/renaming the whole 02 folder.
  10. @Araso did you also tried after removing the conda-env folder ?
  11. you can stick with the latest (the scripts are the same), It's an error on my side.
  12. Holaf_tests is only the branch where I test things, it's broken most of the time ^^ The last things I changed in the test version are what you reported. I add the "bc" command, I fix the bug with the parameters file and the output folder. I updated again the test version and I don't see errors on my side 🤔
  13. @Joly0 @Araso If you use the tag "test" you can try the next version earlier. I changed my mind and added forge in thins version ... Since it's a clean fork of auto1111 instead of having a number on it's own, you must use WEBUI_VERSION="02.forge" It will be installed next to auto1111 and it will use the same environment. If you choose to do so you can remove those two folders : /mnt/user/appdata/stable-diffusion/02-sd-webui/env /mnt/user/appdata/stable-diffusion/02-sd-webui/webui/venv (I will auto-remove them in a future version if this one is working fine) @Araso with a clean install reactor and instant-ID works fine in auto1111, since the test version isn't using the same conda environment I assume you can try to switch to this version to see if that's enough to fix your issue They're also working in forge, but I have a mismatch in cuda version between onxx and torch, so you'll have errors in the log and some parts of the process will be done on CPU (it's still fast, but it will hit the global perf of your computer for a few seconds) In this test version I have update lama cleaner (now IO Paint). It will install in a new folder. @Olivilo I don't support AMD gpu because I can't test easily. You should take a look at Jolyu0 repo's, he is working on it : https://forums.unraid.net/topic/143645-support-stable-diffusion-advanced/?do=findComment&comment=1371508
  14. Thanks for the info, i'll take a look on my side
  15. Yes there is a way With unraid on your container config you have an option at the bottom to add another path. You'll have to add two path : one that points to this one inside the container : /config/outputs and one to : /config/models for example for outputs it should looks like this :