hyperlight-dev / hyperlight-dev/hyperlight-sandbox
Rethink the custom Wit "Run" for using wasi-cli
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 73
- Forks
- 7
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 23
Description
We should use wasi-cli instead of our custom wam interface. This would make it really easy and portable to run other guests. It would also help with #90 if we wanted to extend not just bash but other languages or features too.
This would also make this so that you could do sandbox.run(python ...) or sandbox.run(sh...)` and have just one interface.
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 locating the custom WIT "Run" interface and the current sandbox.run entry point, then compare them with the wasi-cli interface. Consider how one interface would support running both Python and sh, including the extension discussed in issue #90. Done means the custom interface is replaced or integrated so these guest commands can use the same run path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100