rust-lang / rust-lang/rust-playground
Remove network access from the playground
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 268
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 6
Description
Discussed at https://github.com/rust-lang/all-hands-2026/issues/49
The playground uses docker to isolate builds, however, docker is not secure enough (eg https://copy.fail/)
the playground could use lambdas without network access. You can have stdin/stdout streams in this environment.
Once we do this, the playground can run on ECS (because there's no need to run docker anymore).
Local emulators can provide ability to develop Lambdas.
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 with the linked all-hands discussion and inspect the current Docker-based playground isolation. Determine how stdin/stdout builds could run without network access and what local emulator support would be needed. Done means the playground no longer requires Docker, supports networkless execution, and can run on ECS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, rust
- Domain
- cloud, infrastructure, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100