-
Stefy Lanza (nextime / spora ) authored
0.4.96 added gguf>=0.10.0 to requirements.txt, which was half right. Two things about how this image is built that the change missed: * requirements-oci.txt has carried `gguf>=0.9.0` since June, so the dependency was not undeclared after all -- only unsatisfiable. diffusers' GGUFQuantizationConfig refuses anything below 0.10.0 ("requires both PyTorch and GGUF>=0.10.0"), so a 0.9.x install satisfies the line and still cannot load a GGUF pipeline component. Pinned to 0.10.0. * Dockerfile.oci COPIES requirements.txt, requirements-nvidia.txt and requirements-vulkan.txt into the build and then deletes them unused: the RUN installs `-r /tmp/requirements-oci.txt` and nothing else. So for the container image, requirements-oci.txt is the only list that counts. requirements.txt still matters for a host build.sh install, and the in-image upgrade reads BOTH, which is why the entry there is not wasted. No rebuild needed to ship it: coderai-upgrade's delta install takes requirements.txt plus requirements-oci.txt, installs what is new, and the autoupgrade commits the result onto the image tag. Co-Authored-By:Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01S8LAP3ueNzQJtwzhgVbq66
5a9c65f6
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| common | ||
| dinov2cpp | ||
| linux | ||
| runpod | ||
| windows | ||
| build-rpc-server.sh | ||
| cosign.pub | ||
| patch-colibri.py | ||
| patch-k3.py | ||
| setup-salad-venv.sh | ||
| sign-images.sh | ||
| versions.env |