docs.md
CONTAINERS
faster-whisper |
|
---|---|
Requires | L4T >=34.1.0 |
Dependencies | build-essential python cmake ctranslate2 huggingface_hub numpy |
Dependants | whisperx |
Dockerfile | Dockerfile |
RUN CONTAINER
To start the container, you can use the run.sh
/autotag
helpers or manually put together a docker run
command:
# automatically pull or build a compatible container image
./run.sh $(./autotag faster-whisper)
# or if using 'docker run' (specify image and mounts/ect)
sudo docker run --runtime nvidia -it --rm --network=host faster-whisper:35.2.1
run.sh
forwards arguments todocker run
with some defaults added (like--runtime nvidia
, mounts a/data
cache, and detects devices)
autotag
finds a container image that's compatible with your version of JetPack/L4T - either locally, pulled from a registry, or by building it.
To mount your own directories into the container, use the -v
or --volume
flags:
./run.sh -v /path/on/host:/path/in/container $(./autotag faster-whisper)
To launch the container running a command, as opposed to an interactive shell:
./run.sh $(./autotag faster-whisper) my_app --abc xyz
You can pass any options to run.sh
that you would to docker run
, and it'll print out the full command that it constructs before executing it.
BUILD CONTAINER
If you use autotag
as shown above, it'll ask to build the container for you if needed. To manually build it, first do the system setup, then run:
./build.sh faster-whisper
The dependencies from above will be built into the container, and it'll be tested during. See ./build.sh --help
for build options.