Jmeter executor image => Entrypoint Dockerfile

[LDassen]

I was wondering what the 'jmeter' in 'COPY jmeter /bin/runner' should be? Trying to build this image but I don't know what this 'jmeter' should be.
/contrib/executor/jmeter/build/agent/Dockerfile

`# syntax=docker/dockerfile:1
FROM kubeshop/testkube-jmeter-executor:jmeter5.6.2-jdk21-base
COPY jmeter /bin/runner

ENV ENTRYPOINT_CMD="/executor_entrypoint.sh"
WORKDIR /root/

COPY ./contrib/executor/jmeter/scripts/entrypoint.sh /executor_entrypoint.sh
ADD ./contrib/executor/jmeter/plugins/ ${JMETER_CUSTOM_PLUGINS_FOLDER}
ADD ./contrib/executor/jmeter/lib ${JMETER_HOME}/lib/

ENTRYPOINT ["/bin/runner"]`

[vsukhin]

hey, @LDassen Do you want to build Testkube prebuilt execcutors? Because this Dockerfile is prepared for this goal, it contains some logic around it, jmeter is our executor binary name, we renamed it to not match jmeter itself . And we do it automatically

[LDassen]

Could you please tell me how I would create this compiled binary from the jmeter folder?

[LDassen]

I found the way to create the binary file. Clone the repository and then execute the make file inside the jmeter folder. Now i am running into a different problem. When I change the image from the jmeter executor in my k8s cluster to the new image with the binary, I get the following error from testkube:

test container message: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/bin/runner": permission denied: unknown reason: StartError
exit code: 128

Adding chmod +x, chmod 777, chown root:root did not work. Any suggestions @vsukhin ?

[vsukhin]

sounds like, the binay was build for different architecture

[LDassen]

The architecture is correct.. AMD64. We are still getting the same error..

[vsukhin]

Looks like permission issues
@