Closed OrianeN closed 1 year ago
(Edited) Running pip install flash_attn
inside the created container solved the issue, so I'm going to close this issue.
Running
apt install flash_attn
inside the created container solved the issue, so I'm going to close this issue.
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package flash_attn
why can't I find the package 'flash_attn'?even if I update the source using apt-get update
Hi, @BrainWWW. Thanks for the attention.
I used to run the following code on the hf space:
FROM nvcr.io/nvidia/pytorch:22.10-py3
ENV MPLCONFIGDIR /tmp/matplotlib-config
ENV TORCH_CUDA_ARCH_LIST 8.6
WORKDIR /code
COPY . .
RUN pip install --no-cache-dir --upgrade -r /code/requirements.txt
where requirements.txt
need to be updated according to https://github.com/microsoft/unilm/issues/1253#issuecomment-1679956365 now.
According to your feedback, It seems some errors are raised in the installation of xformers
. You can try the solution in https://github.com/microsoft/unilm/issues/1253#issuecomment-1679956365.
Alternatively, huggiing face version is also accessable. You can find it in our readme.
Hope this can help you.
Running
apt install flash_attn
inside the created container solved the issue, so I'm going to close this issue.Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package flash_attn
why can't I find the package 'flash_attn'?even if I update the source using
apt-get update
I'm really sorry to have mislead you, I'm almost sure I actually ran pip install flash_attn
and not apt install
...
I will correct my previous post in order to avoid confusing more people reading this issue.
I've been trying to do the setup to use Kosmos-2 as described in https://github.com/microsoft/unilm/tree/master/kosmos-2#setup - but it seems like dependencies conflicts are preventing a successful installation.
I've created a small Dockerfile (but the first time I've tried the given docker run command as well):
My build command was
nohup docker build -t kosmos2_img . &> docker_build_kosmos2.log &
Yet in both cases I can read the following dependencies conflicts at the end of the
bash vl_setup_xl.sh
script (either run inside the container or during the build):Still I've tried to launch the Gradio demo with
bash run_gradio.sh
inside the created container, but I get the following error:I have tried with and without setting the
--privileged
argument in thedocker run
command - btw I don't understand why it would be necessary to put such a non-secure argument in the case of Kosmos-2.I'm running docker on Ubuntu-18.04, docker version 20.10.24, build 297e128.