Running core tests in docker environment

Hello everyone! I’m currently facing some challenges while configuring my local environment to run discourse tests in a docker container. My main objective is to run the core tests with plugins attached and enabled, rather than focusing solely on plugin tests. I’ve followed the instructions provided here to set up my environment, which worked well for development purposes. However, I’m encountering issues when running the core tests. Maybe there are instructions how can I replicate my environment from github CI?

During the execution of the d/rspec command, I occasionally receive the following error message:

Webdrivers::VersionError:
  Unable to find the latest point release version for 115.0.5790. It seems that you are using a non-production version of Chrome. Please set `Webdrivers::Chromedriver.required_version = <desired driver version>` to a known chromedriver version: https://chromedriver.storage.googleapis.com/index.html

~~~~~~~ SYSTEM TEST ERRORS ~~~~~~~
Unable to find the latest point release version for 115.0.5790. It seems that you are using a non-production version of Chrome. Please set `Webdrivers::Chromedriver.required_version = <desired driver version>` to a known chromedriver version: https://chromedriver.storage.googleapis.com/index.html
Unable to find the latest point release version for 115.0.5790. It seems that you are using a non-production version of Chrome. Please set `Webdrivers::Chromedriver.required_version = <desired driver version>` to a known chromedriver version: https://chromedriver.storage.googleapis.com/index.html
~~~~~~ END SYSTEM TEST ERRORS ~~~~~

Furthermore, when executing the d/rake autospec command or using d/shell along with bundle exec autospec p l=3, I encounter the following stacktrace:

If file watching is not working, you can force polling with: bundle exec rake autospec p l=3
Press [ENTER] to stop the current run
Running Rspec: spec

[repeating multiple times]
** ERROR: directory is already being watched! **

Directory: /src/app/assets/javascripts/node_modules/admin

is already being watched through: /src/app/assets/javascripts/admin

MORE INFO: https://github.com/guard/listen/blob/master/README.md

[after ENTER pressed]
No specs have failed yet! Aborting anyway

Lastly, I’ve noticed intermittent failures in the Qunit tests on http://localhost:4200/tests.

Thank you in advance!