You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get the same error if I use alpine as the base image. The error is coming from inside the container it seems, but it starts with WSL which the container shouldn't have any awareness off. I couldn't find any information online about UtilGetPpid either. The problem could be with any of the following, and I am open to someone helping me to figure out who is at fault!
Docker
WSL
Llamafile
Meta-Llama-3-70B-Instruct-Q4 Llamafile
The text was updated successfully, but these errors were encountered:
This suggests the problem isn't specific to any one llamafile, but rather a more generalized problem with Llamafiles in Docker, or WSL's involvement somehow.
Possibly related, and the only other place I can find useful details about this error: microsoft/WSL#10073
Perhaps someone who better understands how these llamafiles work will get some insight from the discussion in that issue which seems to talk about how binaries are launched within Docker.
Environment:
Docker 24.0.7 on Ubuntu in WSL 2.1.5.0 on Windows 11
Dockerfile.llama
:docker image build --file Dockerfile.llama --tag llama .
docker container run --rm -it llama
docker container run --rm -it --entrypoint /bin/bash llama
./Meta-Llama-3-70B-Instruct.Q4_0.llamafile
from inside the docker container.I get the same error if I use
alpine
as the base image. The error is coming from inside the container it seems, but it starts withWSL
which the container shouldn't have any awareness off. I couldn't find any information online aboutUtilGetPpid
either. The problem could be with any of the following, and I am open to someone helping me to figure out who is at fault!Meta-Llama-3-70B-Instruct-Q4 LlamafileThe text was updated successfully, but these errors were encountered: