microsoft / microsoft/superbenchmark
--no-docker parameter requirements/expectations are missing in documentation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 393
- Forks
- 90
- PR merge metrics
- No merged PRs in 30d
Description
What's the issue, what's expected?:
Attempting to run on remote nodes with the --no-docker option fails because the sb binary is missing on the remote nodes. However, the documentation doesn't provide any instructions or details on the expectations to allow this to work. Do the contents of the docker container need to be (manually) extracted onto the test nodes (somewhere) in advance? Is this option even supported for use on remote test nodes?
How to reproduce it?:
sb run -f config.ini -c default.yaml --no-docker
Log message or shapshot?:
rc=127
command not found
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the documentation for sb run, the --no-docker option, and remote-node execution, then reproduce the reported command: sb run -f config.ini -c default.yaml --no-docker. Done means the documentation clearly states whether remote nodes are supported, what must be installed or placed on them, and how to avoid the reported sb/command not found failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100