wslc: wlsc run does not support --read-only, --cap-drop, --cap-add, etc.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
**Is your feature request related to a problem? Please describe.**
`docker run` supports passing options like `--read-only` or `--cap-drop`. If one uses `runArgs` in the context devcontainers with these options and `wlsc` instead of `docker` for starting the devcontainers, the devcontainer start fails because these options are not known.
**Describe the solution you'd like** `wslc run` should support these options in the future.
**Describe alternatives you've considered** If this is not feasible, it would be nice to have documentation on the currently supported options of `docker run` in `wlsc run`, potentially supported options, and not supported options. One could use this documentation to write scripts/`devcontainer.json` that are supported by `docker run` and `wslc run`.
Contributor guide
Research direction
Start at the wslc run entry point and inspect how command-line options are parsed and passed to devcontainers. Compare its supported options with the named docker run flags, then verify that the requested flags no longer prevent startup; if support is infeasible, document the supported and unsupported options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, docker
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100