Running Gatling main will throw exception with version > 3.10.3

Gatling (Open-Source)
1

Gatling version: 3.11.5 (must be up to date)
Gatling flavor: [ X] java kotlin scala javascript typescript
Gatling build tool: maven gradle sbt bundle npm

I read the guidelines and how to ask a question topics.
I provided a SSCCE (or at least, all information to help the community understand my topic)
I copied output I observe, and explain what I think should be.

I am currently running Gatling version 3.10.3 and works great for me.
I trigger tests running

Gatling.main(new String[]{"-s", "my.simulation.class"});

I am trying to update to version 3.11.5 and getting the error

Exception in thread "main" java.lang.IllegalArgumentException: Can't generate reports if resultsDirectory is not set
	at io.gatling.app.RunResultProcessor.$anonfun$resultsDirectory$1(RunResultProcessor.scala:46)
	at scala.Option.getOrElse(Option.scala:201)
	at io.gatling.app.RunResultProcessor.resultsDirectory(RunResultProcessor.scala:46)
	at io.gatling.app.RunResultProcessor.initLogFileData(RunResultProcessor.scala:52)
	at io.gatling.app.RunResultProcessor.processRunResult(RunResultProcessor.scala:35)
	at io.gatling.app.Gatling$.start(Gatling.scala:96)
	at io.gatling.app.Gatling$.fromArgs(Gatling.scala:48)
	at io.gatling.app.Gatling$.main(Gatling.scala:42)
	at io.gatling.app.Gatling.main(Gatling.scala)
2

You’re not supposed to directly launch the Gatling class, it’s an undocument internal.
The only officially supported runners are the maven, gradle and sbt plugins and the official bundle.
Please stick to these.

3

Thank you! How would you recommend running gatling inside a docker container?

4

This is something we provide in Gatling Enterprise.