-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
auto (AUTOMATIC1111): TypeError: AsyncConnectionPool.__init__() got an unexpected keyword argument 'socket_options' #608
Comments
I fixed it temporarily by editing the dokerfile present in services/AUTOMATIC111/
and by adding a file called requirements_versions.txt in that same folder. here's the content of the file
this applies the fix you mentioned in your post :) |
thanks for the quick reply!, edit: because of your custom
During startup I see a warning too:
(edit: removed duplicate citations) There are some issues about this:
Maybe my CUDA 121 (or I've disabled xformers by editing
Now text2img, img2img etc. fully work! Not sure if I should open a new issue for this, since I'm running your customized Dockerfile |
I believe this issue has been fixed. We only needs to change here:
to the latest commit of AUTOMATIC111 4afaaf8a020c1df457bcf7250cb1c7f609699fa7 which add the httpx==0.24.1 in the requirement file: #13839
|
Thanks all, confirming that updating |
Thanks! I can confirm it, too. It works like this, on a fresh Amazon EC2 instance (edit: still using an Amazon g5.xlarge instance (NVIDIA A10G Tensor-Core-GPU) with an EC2 Deep Learning Base GPU AMI (Ubuntu 20.04) 20231026 (ami-0d134e01570c1e7b4) image):
I left a comment on the related PR here #609 (comment) I think I can close this here now |
Thank you for solving this, and sorry for coming so late to this. I did some updates in #610. Would be great if anyone could test the new version and re-open this issue if the problem remains. |
Thanks a lot @AbdBarho, testing now :) EDIT: confirming the PR build works well for me. Also, good catch on other things like the leftover |
I updated to the latest version, but the same error still occurs." #TypeError: AsyncConnectionPool.init() got an unexpected keyword argument 'socket_options |
Has this issue been opened before?
Describe the bug
I've tried to run the auto (AUTOMATIC1111) UI, following the wiki, and get the following error:
Which UI
auto
Hardware / Software
master
andgit checkout tags/8.1.0
Steps to Reproduce
Additional context
Using a Amazon g5.xlarge instance (NVIDIA A10G Tensor-Core-GPU) with an EC2 Deep Learning Base GPU AMI (Ubuntu 20.04) 20231026 (ami-0d134e01570c1e7b4) image.
By the way, trying the
invoke
UI doesn't work either for me, see #595 (comment)Side note
On a completely different setup on a Google g2-standard-4 machine (Nvidia L4) with a "Deep Learning VM with CUDA 12.1 M112" (c0-deeplearning-common-cu121-v20230925-debian-11-py310) image, I've successfully started AUTOMATIC without Docker but using https://github.com/AUTOMATIC1111/stable-diffusion-webui directly via
but sometimes on
python3 launch.py
I see the same errorgot an unexpected keyword argument 'socket_options'
, but according to the following issues on the https://github.com/AUTOMATIC1111/stable-diffusion-webui/ repo:I could fix it as follows:
But in this https://github.com/AbdBarho/stable-diffusion-webui-docker repo I don't know how to apply this.
The text was updated successfully, but these errors were encountered: