CircleCIでheadless chromeでテストを行う方法

CircleCIを導入し、rspecが実行されるようになりました。
しかし、systemテストでjsも検証できるように設定したchromeが動いていないためか、正しくテストが行われておりません。

circleciの設定ファイルと、rspecのテストでの設定ファイルを記載いたします。
開発環境では問題なく動いており、テストはパスしますし、headlessをコメントアウトすることで、vncでも動作が確認できております。

この辺は理解よりもコピペなところも多く、判断材料として不十分かもしれませんが、
追加記載必要な部分あれば対応させて頂きますので、何かご存知の方おられましたらよろしくお願いいたします。

エラー内容

SocketError:
  Failed to open TCP connection to chrome:4444 (getaddrinfo: No address associated with hostname)

.circleci/config.yml

version: 2
jobs:
  build:
    docker:
      - image: circleci/ruby:2.5.3-node-browsers
        environment:
          RAILS_ENV: test
      - image: circleci/mysql:5.7
        environment:
          - MYSQL_ROOT_HOST: 127.0.0.1
          - MYSQL_ALLOW_EMPTY_PASSWORD: "true"

    working_directory: ~/repo
    steps:
      - checkout
      - restore_cache:
          keys:
            - v1-dependencies-{{ checksum "Gemfile.lock" }}
            - v1-dependencies-
      - run: bundle install --jobs=4 --retry=3 --path vendor/bundle
      - run: yarn install
      - save_cache:
          paths:
            - ./vendor/bundle
          key: v1-dependencies-{{ checksum "Gemfile.lock" }}
      - run: mv config/database.yml.ci config/database.yml
      
      - run: bundle exec rake db:create
      - run: bundle exec rake db:schema:load
      - run: bundle exec rake db:seed

      # Rubocop
      - run:
          name: Rubocop
          command: bundle exec rubocop
      # Rspec
      - run:
          name: Rspec
          command: bundle exec rspec

spec/rails_helper.rb

# frozen_string_literal: true

# This file is copied to spec/ when you run 'rails generate rspec:install'

require 'selenium-webdriver'
# require 'spec_helper'
ENV['RAILS_ENV'] ||= 'test'
require File.expand_path('../config/environment', __dir__)
# Prevent database truncation if the environment is production
abort('The Rails environment is running in production mode!') if Rails.env.production?
require 'rspec/rails'
# Add additional requires below this line. Rails is not loaded until this point!

# Requires supporting ruby files with custom matchers and macros, etc, in
# spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are
# run as spec files by default. This means that files in spec/support that end
# in _spec.rb will both be required and run as specs, causing the specs to be
# run twice. It is recommended that you do not name files matching this glob to
# end with _spec.rb. You can configure this pattern with the --pattern
# option on the command line or in ~/.rspec, .rspec or `.rspec-local`.
#
# The following line is provided for convenience purposes. It has the downside
# of increasing the boot-up time by auto-requiring all files in the support
# directory. Alternatively, in the individual `*_spec.rb` files, manually
# require only the support files necessary.
#
Dir[Rails.root.join('spec', 'support', '**', '*.rb')].sort.each { |f| require f }

# Checks for pending migrations and applies them before tests are run.
# If you are not using ActiveRecord, you can remove these lines.
# begin
#   ActiveRecord::Migration.maintain_test_schema!
# rescue ActiveRecord::PendingMigrationError => e
#   puts e.to_s.strip
#   exit 1
# end
# RSpec.configure do |config|
#   # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures
#   config.fixture_path = "#{::Rails.root}/spec/fixtures"

#   # If you're not using ActiveRecord, or you'd prefer not to run each of your
#   # examples within a transaction, remove the following line or assign false
#   # instead of true.
#   config.use_transactional_fixtures = true
#   config.include SigninSupport, type: :system
#   # RSpec Rails can automatically mix in different behaviours to your tests
#   # based on their file location, for example enabling you to call `get` and
#   # `post` in specs under `spec/controllers`.
#   #
#   # You can disable this behaviour by removing the line below, and instead
#   # explicitly tag your specs with their type, e.g.:
#   #
#   #     RSpec.describe UsersController, :type => :controller do
#   #       # ...
#   #     end
#   #
#   # The different available types are documented in the features, such as in
#   # https://relishapp.com/rspec/rspec-rails/docs
#   config.infer_spec_type_from_file_location!

#   # Filter lines from Rails gems in backtraces.
#   config.filter_rails_from_backtrace!
#   # arbitrary gems may also be filtered via:
#   # config.filter_gems_from_backtrace("gem name")

# end
Capybara.register_driver :remote_chrome do |app|
  url = 'http://chrome:4444/wd/hub'
  caps = ::Selenium::WebDriver::Remote::Capabilities.chrome(
    'goog:chromeOptions' => {
      'args' => [
        'no-sandbox',
        'headless',
        'disable-gpu',
        'window-size=1680,1050'
      ]
    }
  )
  Capybara::Selenium::Driver.new(app, browser: :remote, url: url, desired_capabilities: caps)
end

RSpec.configure do |config|
  config.include FactoryBot::Syntax::Methods
  config.before(:each, type: :system) do
    driven_by :rack_test
  end

  config.before(:each, type: :system, js: true) do
    driven_by :remote_chrome
    Capybara.server_host = IPSocket.getaddress(Socket.gethostname)
    Capybara.server_port = 3000
    Capybara.app_host = "http://#{Capybara.server_host}:#{Capybara.server_port}"
  end
  config.use_transactional_fixtures = true
  config.include Common, type: :system
  config.fixture_path = "#{::Rails.root}/spec/fixtures"
  config.infer_spec_type_from_file_location!
  # ~~~
end