Closed Labmem009 closed 7 months ago
i had the same issue, i listed the Conda environments but i didn't find any of the two environments (lama and LLava), i found that the scripts uses conda activate conda-env-name
so i changed all the line with this command to source activate conda-env-name
, and it worked but i don't understand Why i am getting the "GET / HTTP/1.1" 404 Not Found error, BTW i am running it using WSL2 i also used the Dockerfile which i had to edit so i can build the container.
Given this issue is many months old and there has not been activity I assume it has been resolved or abandoned.
This issue also seems to mix two unrelated things.
GET 127.0.0.1:14122
and the request failingFor 1, I would encourage consumers to use the .devcontainer which scripts the setup. To see manual instructions see: https://github.com/LLaVA-VL/LLaVA-Interactive-Demo/blob/d67e8b8df3f7e749434f286520bbd3193890f862/setup.sh#L10-L13
For 2, this is a side effect of incomplete setup.
2023-11-03 10:40:36 | INFO | stdout | INFO: 127.0.0.1:14124 - "GET / HTTP/1.1" 404 Not Found
EnvironmentNameNotFound: Could not find conda environment: lama You can list all discoverable environments with
conda info --envs
./LLaVA-Interactive-Demo/lama Traceback (most recent call last): File "/LLaVA-Interactive-Demo/lama/../lama_server.py", line 7, in
import hydra
ModuleNotFoundError: No module named 'hydra'
2023-11-03 10:41:06 | INFO | stdout | INFO: 127.0.0.1:14122 - "GET / HTTP/1.1" 404 Not Found
Traceback (most recent call last):
File "/LLaVA-Interactive-Demo/llava_interactive.py", line 7, in
import cv2
ModuleNotFoundError: No module named 'cv2'
And there is no conda env named 'lama', maybe I missed something in setup? But I just followed the README I run run_demo.sh in 'llava_int' env created in setup.