lando / lando/devtool

Use Podman as Default Engine/Orchestrator

Open
#15 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

  • Abstract the containerization engine/orchestrator into universal container management classes that can utilize any container/environment management system such as Docker, Podman, Colima, etc
  • Migrate Docker utilization into this new abstraction layer
  • Add Podman support
  • Make Podman the default

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating where the current Docker engine and orchestration behavior is implemented in the JavaScript codebase. Map the existing Docker usage before defining universal container-management classes, migrating Docker to them, adding Podman support, and making Podman the default; done means all four requirements work together.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, javascript
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.