Closed icodeforyou-dot-net closed 1 month ago
You may well be right. Unfortunately I don't have access to an AMD card so I'm building blind for the target.
The default provisioning script is just an example so feel free to replace it or run without it.
Thanks for getting back to me that quickly!
Unfortunately I don't have access to an AMD card so I'm building blind for the target.
I understand. Maybe I will have some free time and try getting the AMD fork of bitsandbytes into an image. There is also hope that bitsandbytes themselves may add ROCm support in the not too distant future.
The default provisioning script is just an example
Exploring the other path, I would just trim the default provisioning scripts and see if it works with the bare minimum. And then add more stuff again from there.
But maybe you have an idea which things include bitsandbytes
as a dependency? (I am not very familiar with the stable diffusion ecosystem yet)
If I succeed, would you be willing to accept a PR making some changes to the default scripts? And maybe add a few lines in the readme? Provided they don't break things on Nvidia once I am done with them of course :slightly_smiling_face:
I have added a ROCm provisioning script to the config directory. Currently all it does is remove bitsandbytes but I'll add the AMD version at build time asap.
Sorry for the delay but I now have access to AMD hardware so I can make improvements going forward
Trying to run this locally using a simple
docker compose up
, but on ROCm instead of CUDA. Sadly the webui keeps crashing down on me using the default provisioning script. It appears the error is related tobitsandbytes
trying to find CUDA in vain, which is understandable as there is no official ROCm support inbitsandbytes
to this date to my knowledge.AMD does appear to maintain their own fork of
bitsandbytes
here however: https://github.com/ROCm/bitsandbytes/tree/rocm_enabledSo I think there are two questions then.
1) Shouldn't one somehow try to provide the ROCm images built with AMD's fork of
bitsandbytes
?2) Or maybe one should identify all the things that include
bitsandbytes
as a dependency and remove them? Or at least provide people with some documentation which things don't work on ROCm at the moment? Sadly I don't know what that would entail, the provisioning scripts are quite sizable.Any ideas, comments?
Thanks for any help in advance!
I am running this on NixOS, kernel 6.1.77, AMD Radeon Pro W6800 GPU
This is my
docker-compose.yml
:And here is my error message for completeness sake, in case I am interpreting this the wrong way.