Docker環境下でRspecのsystemSpecをSeleniumを使用して動かしたい

Question

環境

ruby 3.0.3
Rails 6.1.7
Docker
Rspec

実現したいこと

docker環境下でRspecのsystemSpecを、ドライバーでseleniumを使用して動かしたい

発生している問題・エラーメッセージ

• 現在docker環境内でchrome-serverという名称でseleniumのchromeイメージからchromeのブラウザ環境を構築し、Rspecのsystemスペックを実行しようとしております。

テスト自体は実行されるのですが、正常にテストが実行されない状況です。
Selenium Grid で実行状況を見てみると、ブラウザが正常に動いていない？ような状態かと思われます。

エラーメッセージを見ると、実際に存在しているはずの要素が存在しないと出ております。

 % docker-compose run --env TEST_BROWSER=chrome --rm web rspec spec/system/events_spec.rb
WARN[0000] Found orphan containers ([awesome_events-webdriver_chrome-1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
[+] Running 2/0
 ⠿ Container awesome_events-db-1             Running                                                                                                                                                                                                    0.0s
 ⠿ Container awesome_events-chrome-server-1  Running                                                                                                                                                                                                    0.0s
Running via Spring preloader in process 32

Events
  /event/:id ページを表示 (FAILED - 1)

Failures:

  1) Events /event/:id ページを表示
     Failure/Error: expect(page).to have_selector "h5", text: event.name
       expected to find css "h5" but there were no matches

     [Screenshot Image]: /awesome_events/tmp/screenshots/failures_r_spec_example_groups_events__event__id_ページを表示_610.png


     # ./spec/system/events_spec.rb:8:in `block (2 levels) in <top (required)>'

Finished in 6.34 seconds (files took 9.48 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/system/events_spec.rb:4 # Events /event/:id ページを表示

いまいちSeleniumやCapybaraのことなどを理解しないまま進めてしまっていたため全く検討つかずの状態となっております。。。
こちらを正常にテスト実行できるようなアドバイスをご教示いただけますと幸いです。

該当のソースコード

docker-compose.yml

version: "3"
services:
  db:
    image: mysql:8.0
    environment:
      MYSQL_ROOT_PASSWORD: password
    volumes:
      - mysql-data:/var/lib/mysql
      - /tmp/dockerdir:/etc/mysql/conf.d/
    ports:
      - 4306:3306
  chrome-server:
    image: selenium/standalone-chrome:96.0
    ports:
      - "7900:7900"
  web:
    build:
      context: .
      dockerfile: Dockerfile
    command: bash -c "rm -f tmp/pids/server.pid && bundle exec rails s -p 3000 -b '0.0.0.0'"
    volumes:
      - .:/awesome_events
      - ./vendor/bundle:/awesome_events/vendor/bundle
    environment:
      TZ: Asia/Tokyo
      RAILS_ENV: development
    ports:
      - "3000:3000"
    depends_on:
      - db
    links:
      - chrome-server
volumes:
  mysql-data:

FROM ruby:3.0

RUN curl https://deb.nodesource.com/setup_14.x | bash

	RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - \
    && echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list

RUN apt-get update -qq && apt-get install -y build-essential nodejs yarn mariadb-client
RUN apt-get install -y vim

ENV APP_PATH /awesome_events

RUN mkdir $APP_PATH

WORKDIR $APP_PATH

COPY Gemfile $APP_PATH/Gemfile
COPY Gemfile.lock $APP_PATH/Gemfile.lock
RUN bundle install

COPY . $APP_PATH

COPY entrypoint.sh /usr/bin/
RUN chmod +x /usr/bin/entrypoint.sh
ENTRYPOINT ["entrypoint.sh"]
EXPOSE 3000

CMD ["rails", "server", "-b", "0.0.0.0"]

spec/support/capybara.rb

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

  config.before(:each, type: :system, js: true) do
    driven_by :selenium, using: ENV.fetch("TEST_BROWSER"), screen_size: [1400, 1400], options: {
      browser: :remote,
      url: "http://#{ENV.fetch("TEST_BROWSER")}-server:4444"
    }
    Capybara.server_host = "0.0.0.0"
    Capybara.app_host = "http://#{ENV.fetch("HOSTNAME")}:#{Capybara.server_port}"
  end
end

rails_helper.rb

# This file is copied to spec/ when you run 'rails generate rspec:install'
require 'spec_helper'
ENV['RAILS_ENV'] ||= 'test'
require_relative '../config/environment'
# 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
  abort e.to_s.strip
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

  # You can uncomment this line to turn off ActiveRecord support entirely.
  # config.use_active_record = false

  # 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

spec/system/events_spec.rb

require 'rails_helper'

RSpec.describe "Events", type: :system, js: true do
  scenario "/event/:id ページを表示" do
    event = FactoryBot.create(:event)
    visit events_url(event)

    expect(page).to have_selector "h5", text: event.name
  end

end

Gemfile

source 'https://rubygems.org'
git_source(:github) { |repo| "https://github.com/#{repo}.git" }

ruby '3.0.3'

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails', branch: 'main'
gem 'rails', '~> 6.1.7'
# Use mysql as the database for Active Record
gem 'mysql2', '~> 0.5'
# Use Puma as the app server
gem 'puma', '~> 5.0'
# Use SCSS for stylesheets
gem 'sass-rails', '>= 6'
# Transpile app-like JavaScript. Read more: https://github.com/rails/webpacker
gem 'webpacker', '~> 5.0'
# Turbolinks makes navigating your web application faster. Read more: https://github.com/turbolinks/turbolinks
gem 'turbolinks', '~> 5'
# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
gem 'jbuilder', '~> 2.7'
# Use Active Model has_secure_password
# gem 'bcrypt', '~> 3.1.7'

# Use Active Storage variant
# gem 'image_processing', '~> 1.2'

# Reduces boot times through caching; required in config/boot.rb
gem 'bootsnap', '>= 1.4.4', require: false

group :development, :test do
  # Call 'byebug' anywhere in the code to stop execution and get a debugger console
  gem 'byebug', platforms: [:mri, :mingw, :x64_mingw]
  gem 'factory_bot_rails'
  gem 'rspec-rails'
end

group :development do
  # Access an interactive console on exception pages or by calling 'console' anywhere in the code.
  gem 'web-console', '>= 4.1.0'
  # Display performance information such as SQL time and flame graphs for each request in your browser.
  # Can be configured to work on production as well see: https://github.com/MiniProfiler/rack-mini-profiler/blob/master/README.md
  gem 'rack-mini-profiler', '~> 2.0'
  gem 'listen', '~> 3.3'
  # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
  gem 'spring'
end

group :test do
  # Adds support for Capybara system testing and selenium driver
  gem 'capybara', '>= 3.26'
  gem 'selenium-webdriver', '>= 4.0.0.rc1'
  # Easy installation and use of web drivers to run system tests with browsers
  gem 'webdrivers'
  gem 'launchy'
end

# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]
gem 'hamlit-rails'
gem 'omniauth', '~> 2.1'
gem 'omniauth-github', '~> 2.0', '>= 2.0.1'
gem 'omniauth-rails_csrf_protection', '~> 1.0', '>= 1.0.1'
gem 'rails-i18n', '~> 7.0', '>= 7.0.6'