Closed teamblubee closed 1 month ago
Re the first issue, we have simplified the CLI to only requiring llama stack build
. Wondering if you have link the documentation where you have seen the llama stack build --name test
command. Wanted to make it consistent with the actual implementation.
llama stack build -h
usage: llama stack build [-h] [--config CONFIG]
Build a Llama stack container
options:
-h, --help show this help message and exit
--config CONFIG Path to a config file to use for the build
Re the second issue, the error message suggests it may be cause by https://github.com/meta-llama/llama-stack/blob/736092f6bc9887552d11b7c6f266c6ac4087a0a8/llama_toolchain/common/exec.py#L43 running WSL, where process = subprocess.Popen
may fail.
The instructions that still shows using command line arguments here: https://github.com/meta-llama/llama-stack/blob/main/docs/cli_reference.md#step-32-build-a-distribution
specifically here:
Step 3.2: Build a distribution
Let's imagine you are working with a 8B-Instruct model. The following command will build a package (in the form of a Conda environment) and configure it. As part of the configuration, you will be asked for some inputs (model_id, max_seq_len, etc.) Since we are working with a 8B model, we will name our build 8b-instruct to help us remember the config.
llama stack build local --name 8b-instruct
The WSL issue is was fixed with dos2unix
somehow on git pull on windows then using going into WSL the files somehow got corrupted.
If you can update the above commands we can call this issue close.
The instructions that still shows using command line arguments here: https://github.com/meta-llama/llama-stack/blob/main/docs/cli_reference.md#step-32-build-a-distribution
Thanks! Could you run git pull
, and check again? It have been updated!
Running inside WSL
Cloned the repo made it to trying to build a model. First issue
llama stack build doesn't work
After that we just manually go through the configuration, that fails with a missing file error:
the referenced file that fails to open is there:
Those errors were a bit misleading as I kept chasing them down. The main issue is that this doesn't build on windows and in WSL somehow all the files were corrupted. I had to
dos2unix
the entire cloned git repo and then those errors went away.