Add containerd + Rancher Desktop as a supported runtime for local usage
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
Currently, we only support Rancher Desktop as a runtime when it uses dockerd. Rancher OS also supports containerd, and uses that as a default. Since Rancher Desktop creates a VM for Windows and Mac, this is a cross-platform concern.
Since containerd is not API compatible with Docker, we will need a separate runtime implementation for containerd. Right now, the Docker runtime implements a bunch of logic needed for local workloads (e.g. the egress proxy and DNS server, so we may want to split up the Docker layer in two: The lower layer that talks directly to the Docker Client and implements low level operations like container creation, and a higher layer which is responsible for orchestrating the deployment of the workload.
Contributor guide
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 examining the existing Docker runtime implementation and the logic it provides for local workloads, including the egress proxy and DNS server. Determine how a separate containerd runtime could support Rancher Desktop's default mode on Windows and Mac, and define completion as working local usage without dockerd.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100