Capybara Unable to find Mozilla geckodriver


I have a Rails 5.0.2 app and I’m using rspec and capybara for testing.
I’m using firefox for my javascript enabled feature specs.
On my local machine these are working ok.
When I push to master and CircleCI runs my specs I get the following error:

Unable to find Mozilla geckodriver. Please download the server from and place it somewhere on your PATH. More info at

I’m using ruby 2.4, capybra 2.12.1.

I had assumed this would be a fairly standard setup but there doesn’t seem to be any info about this specific error on CircleCI.

Any suggestions gratefully received!


So I fixed this by downgrading my firefox to version 44 and setting my selenium-webdriver gem to 2.53.1

A few of my specs had to be adjusted to work with these different versions but CircleCi seems to be able to run them now which is nice.


I tried and failed to get geckodriver setup by manually attempting to installing it and still failed. If anyone has managed to get this to work, please chime in.


Possibly having path issues. Try this code snippet:

    - mkdir drivers
    - wget && tar -zxvf geckodriver-v0.11.1-linux64.tar.gz:
        pwd: drivers

Adjust version as needed :slight_smile:


I tried this out, but I’m still getting the same error:

Unable to find Mozilla geckodriver. Please download the server from and place it somewhere on your PATH.

Does this code snippet actually place the drivers directory on the containers path, or just unzip the tar to that directory?

I’m using the latest version of selenium-webdriver (3.3.something) and trying to use geckodriver 0.15.

Are these versions supported? If not I’m not sure how I can manage two sets of selenium/firefox for circleci and for my local dev environments.


Hi there, could you answer Zacharw;s question? I’m having the same issue and would love to know! :slight_smile: thanks!


Hey! i was able to fix this by adding the path to my PATH:



I ended up fixing it by setting up a chrome selenium driver instead of firefox - that worked on circleci out of the box.

In spec_helper.rb:

Capybara.register_driver :chrome do |app|, :browser => :chrome)

Capybara.javascript_driver = :chrome

You will have to brew install chromedriver on your local machine.


@zacharyw you didn’t have to add a Docker image or anything? I tried adding that with no luck. Tried pretty much everything I could find on here with no luck.

version: 2
      - image: circleci/ruby:2.3.4
      - image: selenium/standalone-chrome:latest
    working_directory: ~/repo
      - checkout
      - run: echo "Running from .circleci/config.yml"
      - run: echo $CC_TEST_REPORTER_ID
      - run: ruby -v
      - run: gem install bundler -v 1.15.4
      - run: bundler -v
      - restore_cache:
          key: rails-{{ arch }}-{{ checksum "Gemfile.lock" }}
      - run: bundle check --path=vendor/bundle || bundle install --path=vendor/bundle --jobs=4 --retry=3
      - save_cache:
          key: rails-{{ arch }}-{{ checksum "Gemfile.lock" }}
            - vendor/bundle
      - run:
          name: Install latest version of ChromeDriver Sample
          command: |
            sudo wget
            sudo unzip
            sudo rm
            sudo mv chromedriver /usr/bin/
            sudo chmod 777 /usr/bin/chromedriver
            sudo apt-get install libxi6 libgconf-2-4
            sudo apt-get -y install xvfb gtk2-engines-pixbuf
            sudo apt-get -y install xfonts-cyrillic xfonts-100dpi xfonts-75dpi xfonts-base xfonts-scalable
            sudo apt-get install xvfb
            sudo apt-get -y install imagemagick x11-apps
      - run: rubocop
      - run: curl -L > ./cc-test-reporter
      - run: chmod +x ./cc-test-reporter
      - run: ./cc-test-reporter before-build
      - run: bundle exec rspec spec
      - run: ./cc-test-reporter after-build --exit-code $? || true

closed #10