CliContainerEngine: verify create/start -a -i and the inspect "no such" wording on Podman and nerdctl
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 67/100
Research direction
Start by reading CliContainerEngine and the ContainerIntegration tests under tests/OKF4net.Tests. Run dotnet test tests/OKF4net.Tests --filter Category=ContainerIntegration with CliContainerEngine("podman") and CliContainerEngine("nerdctl"). Check whether create/start flags, exit-code and stream handling, inspect's missing-container wording, and rm -f behavior match the assumptions; document or fix any differences.
Written by the indexing model from the issue text.
Description
Follow-up to #110 (fixed by #231 and #227).
CliContainerEngine was only ever run against Docker 29.4.1 (Windows). Two assumptions are unverified on Podman and nerdctl, which the class is documented to cover:
- A run is
createthenstart -a -i: thatstart -a -ipropagates the container's exit code and carries stdin/stdout/stderr, and thatcreateaccepts the same isolation flags (--rm,--read-only,--tmpfs,--cap-drop,--security-opt,--memory,--cpus,--pids-limit). - Teardown counts a container as absent only when
inspectexits non-zero and stderr contains "no such" (case-insensitive). If an engine words it differently, teardown simply runs to the end of its budget instead of returning early (never a leak, only slower).
Also unverified: their rm -f exit code for an unknown name.
To close: run dotnet test tests/OKF4net.Tests --filter Category=ContainerIntegration with a CliContainerEngine("podman") / ("nerdctl") and fix or document whatever differs.
- Dominant language
- C#
- Stars
- 4
- Forks
- 1
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 32
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 jchable/okf4net
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
.NET bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
test
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area/backend type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
umbraco/Umbraco-CMS#24668 · 1 comment ·
Maintainers usually reply within 1 day
-
Pri3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MicrosoftDocs/windows-dev-docs#6205 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
area-ai untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/extensions#7956 ·
Maintainers usually reply within 1 day