[Gatling-TS] : DockerFile issue with path

Gatling (Open-Source)
1

Gatling version: 3.13.103
Gatling flavor: typescript
Gatling build tool: npm

Hello Dear Community,

I wanted to work on a performance project using the Gatling-TS version but I have an issue creating a DockerFile.

Here are the steps to reproduce :

  • I downloaded the “gatling-js-demo-main” installed the project (npm install) and launched it to verify the installation. It worked perfectly.

  • I created a really simple DockerFile :

FROM node:22-alpine as base

WORKDIR /app

#copy package.json to docker container
COPY . .

#install package.json dependency
RUN npm i

#launch gatling cmd
RUN npx gatling run
  • Build the Docker Container using

docker build -t gatling-demo . --no-cache

I have the following error : 

node:internal/errors:983
  const err = new Error(message);
              ^

Error: Command failed: "/root/.gatling/coursier/2.1.12/cs" fetch --classpath "io.gatling.highcharts:gatling-charts-highcharts:3.13.1" "io.gatling:gatling-jvm-to-js-adapter:3.13.103" "io.gatling:gatling-enterprise-plugin-commons:1.9.8" "org.graalvm.polyglot:js-community:24.1.1"
/root/.gatling/coursier/2.1.12/cs: exec: line 26: /root/.gatling/graalvm/23.0.0/bin/java: not found

    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at ChildProcess.exithandler (node:child_process:419:12)
    at ChildProcess.emit (node:events:518:28)
    at maybeClose (node:internal/child_process:1104:16)
    at ChildProcess._handle.onexit (node:internal/child_process:304:5) {
  code: 127,
  killed: false,
  signal: null,
  cmd: '"/root/.gatling/coursier/2.1.12/cs" fetch --classpath "io.gatling.highcharts:gatling-charts-highcharts:3.13.1" "io.gatling:gatling-jvm-to-js-adapter:3.13.103" "io.gatling:gatling-enterprise-plugin-commons:1.9.8" "org.graalvm.polyglot:js-community:24.1.1"',
  stdout: '',
  stderr: '/root/.gatling/coursier/2.1.12/cs: exec: line 26: /root/.gatling/graalvm/23.0.0/bin/java: not found\n'
}

Node.js v22.11.0

Does anyone encounter the same issue ?

Thank you and have a good day,

Victor

2

Hello,

Sorry but we can’t help with repackaging Gatling to deploy on remote machines as this is one of the features we provide with Gatling Enterprise.

Thanks for your understanding.
Regards

1 Like
3

Hello Stéphane,

I do understand the conflict of interest. I just wanted to share a potential issue within the TS package.

Have a good day,

Victor

4

Thanks.

FYI, we’re currently working on making this module more “corporate network” friendly.

5

Thank you for the information.

Having the possiblity to use an alpine could be a real benefit :slightly_smiling_face:

6

Sorry, but could you please explain why? I fail to see how this would help with local development.

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.