Conversation
1. The k6 executable from the latest .msi installer says it does not know the `init` parameter: ``` C:\>k6 init ERRO[0000] unknown command "init" for "k6.exe" ``` I suppose `new` should be used instead, like on Linux. Also I changed Windows commands to run k6 executable directly instead of via Docker.
|
|
|
I encountered the same issue, but I cannot use Running |
heitortsergent
left a comment
There was a problem hiding this comment.
@sabi0 thanks for the opening the PR, and sorry about the delay!
Based on @PontusMagnusson feedback, it seems that keeping the Docker commands for now would help most users, I left some comments to revert that and just changing the init command to new.
|
|
||
| ```windows | ||
| PS C:\> docker run --rm -i -v ${PWD}:/app -w /app grafana/k6 init | ||
| PS C:\> k6 new |
There was a problem hiding this comment.
| PS C:\> k6 new | |
| PS C:\> docker run --rm -i -v ${PWD}:/app -w /app grafana/k6 new |
|
|
||
| ```windows | ||
| PS C:\> cat script.js | docker run --rm -i grafana/k6 run - | ||
| PS C:\> k6 run script.js |
There was a problem hiding this comment.
| PS C:\> k6 run script.js | |
| PS C:\> cat script.js | docker run --rm -i grafana/k6 run - |
|
|
||
| ```windows | ||
| PS C:\> cat script.js | docker run --rm -i grafana/k6 run --vus 10 --duration 30s - | ||
| PS C:\> k6 run --vus 10 --duration 30s script.js |
There was a problem hiding this comment.
| PS C:\> k6 run --vus 10 --duration 30s script.js | |
| PS C:\> cat script.js | docker run --rm -i grafana/k6 run --vus 10 --duration 30s - |
|
|
||
| ```windows | ||
| PS C:\> cat script.js | docker run --rm -i grafana/k6 run - | ||
| PS C:\> k6 run script.js |
There was a problem hiding this comment.
| PS C:\> k6 run script.js | |
| PS C:\> cat script.js | docker run --rm -i grafana/k6 run - |
What?
The k6 executable from the latest .msi installer says it does not know the
initparameter:I suppose
newshould be used instead, like on Linux.Also I changed Windows commands to run k6 executable directly instead of via Docker.
Checklist
npm startcommand locally and verified that the changes look good.docs/sources/nextfolder of the documentation.docs/sources/v{most_recent_release}folder of the documentation.Related PR(s)/Issue(s)