stable-diffusion
stable-diffusion copied to clipboard
Please help me run stable diffusion
D:\stable diffusion\stable-diffusion-webui>git pull fatal: detected dubious ownership in repository at 'D:/stable diffusion/stable-diffusion-webui' 'D:/stable diffusion/stable-diffusion-webui' is on a file system that doesnot record ownership To add an exception for this directory, call:
git config --global --add safe.directory 'D:/stable diffusion/stable-diffusion-webui'
D:\stable diffusion\stable-diffusion-webui>pause
Для продолжения нажмите любую клавишу . . .
venv "D:\stable diffusion\stable-diffusion-webui\venv\Scripts\Python.exe"
Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug 1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
Commit hash:
git config --global --add safe.directory 'D:/stable diffusion/stable-diffusion-webui/repositories/stable-diffusion-stability-ai'
i had same problem, you should open Git Bash and enter command git config --global~ (last line)
there and close. then run webui-user.bat again and if it asks to call some command again to add an exception for directory then repeat previous steps. i was supposed to do this 3 times
I had a very similar if not identical error and found the solution. Steps to follow:
- Open the Start menu and look for "Environment Variables".
- Select "Edit system environment variables".
- Click the "Environment Variables" button.
- In the "System Variables" section, find the PATH variable and click the "Edit" button.
- Click the "New" button and add the path to the git application (e.g. "C:\Program Files\Git\bin").
- Click "OK" to save your changes and close all windows.
Once you have added the git application path to the PATH environment variable, try running the .bat file again. I hope this helps you fix the problem.
Curiosity: Chat GPT solved it for me, because I had no idea. :-)
From the error-message I am assuming your question is about the stable diffusion webui by AUTOMATIC1111. Please be aware this is a third-party tool and we cannot provide any support for it. You may want to look into the issues there, both closed and open to find out if other people have reported this problem before, or open a new issue if that is not the case.