Repository navigation
Unable to d/l Kokoro v1.0 model files w/ Docker Compose or manual d/l #494
|
After building v0.7.0-rc1 successfully earlier today, I tried to rebuild it again. The build failed on downloading the model. The listing shows the crash from the Compose, and the attempt from collecting the model update manually. kokoro-tts-1 | Downloading Kokoro v1.0 model files kokoro-tts-1 exited with code 1 OK, let's try this manually... PS C:\Users\pavil\Kokoro-FastAPI\docker\gpu> cd ../.. |
Replies: 5 comments 1 reply
|
Looks like the first part was a DNS resolution error finding The second part looks like it is working as expected when that happens, it only got a partial download or error message dumped in the models place and rejected it. I'll take a look for a patch to tighten up the handling for retries and verification with a more informative error message In the current shape, it should self-heal once the DNS resolves again if I'm right |
|
I wisely(!) stored the full working directory for the earlier build (the v0.7.0-rc1 from 29 July) before trying the most recent, failed build. Building a fresh FastKoko container from that directory worked as expected (model's residing in the directory). So, my guess is access to the Kokoro model is borken or the present repo has an error in how it looks for the Kokoro model. |
|
So I restarted everything, tucked the working directory in a dark corner (changed the name of the root folder), and... #2 [internal] load build definition from Dockerfile.optimized #3 resolve image config for docker-image://docker.io/docker/dockerfile:1
|
|
@RBEmerson970 if it's failing on line 1 : Did you change any settings (VPN, your router, Docker, etc) between the first run that worked, and the next one that failed? You can do a cheap test by running something like: (or grabbing any other stable public url). If it fails too, that would confirm it. If it passes, try re-running the build I pushed a change to |
|
There were no changes at my end - just "worked then, didn't work later" after I tried to catch up on the changes to the repo. Or, was a problem, now there isn't. |
@RBEmerson970 if it's failing on line 1 :
# syntax=docker/dockerfile:1, it looks like the same issue as before, not related to anything in the repo specifically. That pulls from dockers own registry, the Docker VM isn't able to resolve properly to the outside world (that happens separately from a clone, which is running on your host network).Did you change any settings (VPN, your router, Docker, etc) between the first run that worked, and the next one that failed? You can do a cheap test by running something like:
(or grabbing any other stable public url). If it fails too, that would confirm it. If it passes, try re-running the…