Use Podman as Default Engine/Orchestrator
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, javascript
- Domain
- devops, infrastructure
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.
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
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 lando/devtool
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
Difficulty 2/5 Under an hour Newbie friendliness 85/100
capricorn86/happy-dom#2474 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
juice-shop/juice-shop#3662 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Add unit-test coverage for API URL resolution and device authentication error handlingPossibly taken @Simranjit8933 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
fossasia/eventyay-checkin#170 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day