Fix: Resolve dependency conflict in Docker build #170
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a dependency conflict that prevents the
Dockerfilefrom building a working image.The Problem
The previous installation process installed
torchandwhisperlivekitin separate steps. This causedpip's dependency resolver to incorrectly handle a version conflict betweentorch(which requirestriton>=3.0) andwhisperlivekit(which requirestriton<3.0).The result was a silent downgrade of
torch, leading to a container that would crash on startup with anOSError: undefined symbolintorchaudio.The Solution
This change resolves the issue by:
RUNcommand.--extra-index-urlinstead of--index-urlto ensurepipcan access both the main PyPI repository and the special PyTorch index.This allows
pipto see all dependency constraints at once and install a consistent, compatible set of packages, resulting in a successful build and a working container.