search

artilleryio / artillery

The complete load testing platform. Everything you need for production-grade load tests. Serverless & distributed. Load test with Playwright. Load test HTTP APIs, GraphQL, WebSocket, and more. Use any Node.js module.
https://www.artillery.io
Mozilla Public License 2.0
8.04k stars 511 forks source link

Latest Docker image doesn't include `artillery` command #1394

Open davistrent opened 2 years ago

davistrent commented 2 years ago

The latest Docker container image does not include the artillery command in the /bin directory. The only command available is run. run appears to be the artillery command, but does not match the usage documentation.

In the container, run must be used as artillery. e.g. run run /path/to/script ...

Latest container:

https://hub.docker.com/layers/artillery/artilleryio/artillery/2.0.0-14/images/sha256-8a1e0a395dbe0380b52b1632e73208c3fb0bc4d77eda262efdf5221bee5e8210

pedropinheiro75 commented 2 years ago

I also facing this issue here!

I'm trying to follow the docs on how to run the artillery on the GitHub Actions and I need to change the binary call from /home/node/artillery/bin/artillery run tests/performance/socket-io.yml to /home/node/artillery/bin/run run tests/performance/socket-io.yml using the latest docker image tag.

chengyak commented 1 year ago

any update on this issue? I can use /home/node/artillery/bin/run as workaround but that looks strange. also, when it is fix, my pipeline my break?

xwiz commented 1 year ago

How does one add curl to the docker image?

nbpeth commented 1 year ago

welp I just ran into this, so curious if there is any movement.

nbpeth commented 1 year ago

FYI I reconciled the command from the tutorial with the package and that seems right, the command should be /home/node/artillery/bin/run run <path/to/test.yaml>

it is working for me.

I also noticed that the version artillery/2.0.0-dev9 has the run command is replaced by artillery. the latest release 2.0.0-29 still uses run