Atinoda / text-generation-webui-docker

Docker variants of oobabooga's text-generation-webui, including pre-built images.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Alltalk_tts extension doesn't run properly?

haxxorboi opened this issue · comments

Is anyone able to get the alltalk_tts extension (https://github.com/erew123/alltalk_tts) to run properly in this container? I've done both the webui and standalone routes, but both throw errors. I'm running this container in Unraid, which otherwise has been fine. Coqui and silero tts extensions seems to work fine.

Install has been using the alltalk_tts github instructions (https://github.com/erew123/alltalk_tts?tab=readme-ov-file#-quick-setup-text-generation-webui--standalone-installation). Console into the TGW-docker container and an example workflow for running with TGW option being:

#Put alltalk_tts git repo into extensions folder
cd extensions && git clone https://github.com/erew123/alltalk_tts
#Install curl, as the start_linux.sh script needs it
apt install curl -y
#Run the webui start_linux.sh script to get the setup dependencies, like conda, installed, which the alltalk scripts need to work
cd .. && ./start_linux.sh
#select options Nvidia and N for old CUDA version
#Start the env, which alltalk_tts atsetup.sh needs
./cmd_linux.sh
#Make the alltalk config script executable and start execution
cd extensions/alltalk_tts && chmod +x ./atsetup.sh && bash ./atsetup.sh
#option 1 to start install

Alltalk diag log and TGW container log when attempting to use Alltalk extension attached. Thoughts?

alltalk_diag.txt
tgw_alltalk_log.txt

Hi @haxxorboi, did you manage to get this working? I can suggest to clone the extension repo to the extensions folder, then map the whole extensions folder or just the alltalk_tts folder as a volume, then set the environment variable BUILD_EXTENSIONS_LIVE="alltalk_tts" to install its dependencies on container launch. There are examples in the docker-compose.yml that should keep you on track.