seanpedrickcase commited on
Commit
619a281
1 Parent(s): 16dc1f9

Unspecifying gradio and spacy in requirements, then reinstalling latest gradio afterwards in Dockerfile. All to try to avoid typer conflict

Browse files
Files changed (2) hide show
  1. Dockerfile +3 -1
  2. requirements.txt +1 -1
Dockerfile CHANGED
@@ -14,7 +14,9 @@ WORKDIR /src
14
 
15
  COPY requirements.txt .
16
 
17
- RUN pip install -r requirements.txt
 
 
18
 
19
  # Set up a new user named "user" with user ID 1000
20
  RUN useradd -m -u 1000 user
 
14
 
15
  COPY requirements.txt .
16
 
17
+ RUN pip install -r requirements.txt --no_cache_dir
18
+
19
+ RUN pip install gradio==4.31.0 --no_cache_dir
20
 
21
  # Set up a new user named "user" with user ID 1000
22
  RUN useradd -m -u 1000 user
requirements.txt CHANGED
@@ -8,7 +8,7 @@ pikepdf==8.15.1
8
  pandas==2.2.2
9
  spacy # Not specified as latest versions create a conflict with latest versions of gradio
10
  en_core_web_lg @ https://github.com/explosion/spacy-models/releases/download/en_core_web_lg-3.7.1/en_core_web_lg-3.7.1.tar.gz
11
- gradio==4.31.0
12
  boto3==1.34.103
13
  # Following are not currently necessary for the app, may be added for improved pdf parsing in future
14
  #unstructured
 
8
  pandas==2.2.2
9
  spacy # Not specified as latest versions create a conflict with latest versions of gradio
10
  en_core_web_lg @ https://github.com/explosion/spacy-models/releases/download/en_core_web_lg-3.7.1/en_core_web_lg-3.7.1.tar.gz
11
+ gradio # Not specified as latest versions create a conflict with latest versions of spacy
12
  boto3==1.34.103
13
  # Following are not currently necessary for the app, may be added for improved pdf parsing in future
14
  #unstructured