You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @luketn how are your? I am writing you since i am having an error running the docker-compose run k6 run /scripts/ewoks.js
I have clone the repository and from docker-k6-grafana-influxdb folder after running the docker-compose up -d influxdb grafana (the container is running)
But when i run the docker-compose run k6 run /scripts/ewoks.js I am getting the following error:
Do you know what could be the root cause? i am running from mac
Thanks a lot isn advance!
The text was updated successfully, but these errors were encountered:
docker compose up --build -d influxdb grafana
echo"--------------------------------------------------------------------------------------"echo"Load testing with Grafana dashboard http://localhost:3000/d/k6/k6-load-testing-results"echo"--------------------------------------------------------------------------------------"
docker compose run --rm -it k6
Then I run this bash command from root directory:
./run-load-test.sh
Inside docker container terminal I run following command:
k6 run /scripts/ewoks.js
Problem was in resolving path to ewoks.js script. When I ran command docker compose run --rm k6 run /scripts/ewoks.js, the path to script was resolved in my Windows context and not in k6 container context. So docker container tried to run script located in C:/Program Files/Git/scripts/ewoks.js.
Hi @luketn how are your? I am writing you since i am having an error running the docker-compose run k6 run /scripts/ewoks.js
I have clone the repository and from docker-k6-grafana-influxdb folder after running the
docker-compose up -d influxdb grafana
(the container is running)But when i run the
docker-compose run k6 run /scripts/ewoks.js
I am getting the following error:Do you know what could be the root cause? i am running from mac
Thanks a lot isn advance!
The text was updated successfully, but these errors were encountered: