Any chance of supporting crun instead of runc?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, rust
- Domain
- infrastructure
Research direction
The issue names no files, entry points, or tests. Start by locating where runc support is handled and checking any related tests or documentation, then determine the compatibility requirements for crun; done means crun can be selected and device hot-plugging works as expected.
Written by the indexing model from the issue text.
Description
As title, crun has started replacing runc in some distros would it be possible to support it
- Dominant language
- Rust
- Stars
- 16
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
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.
More from lowRISC/container-hotplug
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
lowRISC/container-hotplug#16 ·
All issues in lowRISC/container-hotplug
Similar issues
-
Browser (wasm) relay client cannot connect to relays whose URL has a trailing-dot FQDN hostname Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
n0-computer/iroh#4550 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
paritytech/zombienet-sdk#591 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
farion1231/cc-switch#7638 · 1 comment ·
-
onnx-ir re-exports ModelProto and GraphProto but not NodeProto, AttributeProto and AttributeType Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100