Latest Docker image doesn't include artillery command
#1394
Comments
|
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 |
davistrent
changed the title
artillery commandartillery command
The currently built container image works fine if you want to invoke artillery through a single docker command. But if you want to run multiple artillery commands in the same container instance, or if you want to use Artillery's container image as a base layer, then you ran into issues such artilleryio#1394. The issue us that the executable in the path is named `run` instead of `artillery`. To address this while maintain compatibility for any users depending on the existing executable we can run an `npm install` which will setup artillery as if it had been installed globally. Fixes artilleryio#1394.
Fixes artilleryio#1394. The currently built container image works fine if you want to invoke artillery through a single docker command. But if you want to run multiple artillery commands in the same container instance, or if you want to use Artillery's container image as a base layer, then you ran into issues such artilleryio#1394. The issue us that the executable in the path is named `run` instead of `artillery`. To address this while maintain compatibility for any users depending on the existing executable we can run an `npm install` which will setup artillery as if it had been installed globally.
|
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? |
|
How does one add curl to the docker image? |
|
welp I just ran into this, so curious if there is any movement. |
|
FYI I reconciled the command from the tutorial with the package and that seems right, the command should be it is working for me. I also noticed that the version |
The latest Docker container image does not include the
artillerycommand in the/bindirectory. The only command available isrun.runappears to be theartillerycommand, but does not match the usage documentation.In the container,
runmust be used asartillery. e.g.run run /path/to/script ...Latest container:
https://hub.docker.com/layers/artillery/artilleryio/artillery/2.0.0-14/images/sha256-8a1e0a395dbe0380b52b1632e73208c3fb0bc4d77eda262efdf5221bee5e8210
The text was updated successfully, but these errors were encountered: