title: Mounting of Docker volume results in a "Scrapy - no active project"
body: <p>I am writing up a scrapy python project that scraps data for a future ML project. I decided to containerize my project in Docker - below is my <code>DockerFile</code>:</p>
  <pre><code>FROM python:3.9.12-slim-buster
  
  WORKDIR /app
  
  RUN apt-get update &amp;&amp; apt-get install -y git
  
  RUN pip3 install --upgrade pip
  
  COPY requirements.txt requirements.txt
  
  RUN pip install -r requirements.txt
  
  ADD . /app
  </code></pre>
  <p>I am able to run the following command and my scraper will run successfully:</p>
  <pre><code>docker run -it  ufc-stats-scraper scrapy crawl ufc_future_fights -o future.csv -t csv
  </code></pre>
  <p>output:</p>
  <pre><code>....
   'robotstxt/response_status_count/404': 1,
   'scheduler/dequeued': 53,
   'scheduler/dequeued/memory': 53,
   'scheduler/enqueued': 53,
   'scheduler/enqueued/memory': 53,
   'start_time': datetime.datetime(2022, 4, 20, 2, 4, 7, 365309)}
  2022-04-20 02:04:08 [scrapy.core.engine] INFO: Spider closed (finished)
  </code></pre>
  <p>However, the scraped data is stored in the future.csv file, which is local to the container. I read online that I should use the <code>-v</code> command and mount the containers folder. Below is the command that I am trying to use:</p>
  <pre><code> docker run -it -v ${PWD}:/app ufc-stats-scraper scrapy crawl ufc_future_fights -o future.csv -t csv
  </code></pre>
  <p>However, I am getting the error message below when running this command:</p>
  <pre><code>Scrapy 2.6.1 - no active project
  
  Unknown command: crawl
  
  Use &quot;scrapy&quot; to see available command
  </code></pre>
  <p>I'm fairly new to Docker but was wondering if anyone had any input on what I could be doing wrong here. Thanks!</p>
  <p>Update:</p>
  <p>I started a bash session on two versions of my docker image. One session was unmounted and the other was mounted. The app folder contained all of the repos files in the unmounted session. The weird thing is that the app folder is completely empty on the mounted session. This would explain why the error message reads &quot;no active project&quot;. I am really confused why the mounted image is empty though.</p>
  <p>I feel like I might be misunderstanding how the the Docker bind mount stuff works.</p>