⚡️ Feature: Podman Quadlets in addition to docker-compose
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- docker, docker-compose
- Domain
- devops, documentation, infrastructure
Research direction
Review the repository's existing docker-compose examples and compare them with output from the linked Podlet conversion tool. First clarify which Quadlet patterns maintainers want to support; done means adding agreed examples that demonstrate equivalent configurations and documenting how to use them.
Written by the indexing model from the issue text.
Description
Feature Description
It would be great if there were a few examples in this repo of accomplishing the same design pattern with Quadlets.
Problem It Solves
Podman Quadlets have improved security, reliability, and maintainability over docker-compose. Rootless operation, UID mapping, and systemd integration are huge wins from a server admin perspective.
Proposed Solution
To get started there's a conversion tool:
https://github.com/containers/podlet
I'm not sure in what shape the maintainers would want to see quadlet support as there's a spectrum of options, so I thought I'd start the conversation first before trying any coding or writing.
Would you be willing to work on this feature?
- Yes, I'd like to implement this feature
- I could help with parts of this feature
- No, I'm just suggesting the feature
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 127
- Avg merge
- 15h 58m
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from tailscale-dev/ScaleTail
-
new service
Difficulty 3/5 1-2 days Newbie friendliness 45/100
tailscale-dev/ScaleTail#341 ·
Maintainers usually reply within 1 day
-
new service
Difficulty 4/5 3-5 days Newbie friendliness 48/100
tailscale-dev/ScaleTail#335 ·
Maintainers usually reply within 1 day
-
new service
Difficulty 4/5 3-5 days Newbie friendliness 30/100
tailscale-dev/ScaleTail#325 ·
Maintainers usually reply within 1 day
-
new service
Difficulty 3/5 1-2 days Newbie friendliness 52/100
tailscale-dev/ScaleTail#323 ·
Maintainers usually reply within 1 day
-
new service
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
tailscale-dev/ScaleTail#322 ·
Maintainers usually reply within 1 day
All issues in tailscale-dev/ScaleTail
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
QuantEcon/lecture-python-programming#642 ·
Maintainers usually reply within 1 day
-
area/config area/profiles comp/cli needs-decision P3 sweeper:risk-compatibility type/feature
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NousResearch/hermes-agent#133697 ·
Maintainers usually reply within 1 day
-
enhancement needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
core
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vectorize-io/hindsight#5279 ·
Maintainers usually reply within 1 day