CliContainerEngine: verify create/start -a -i and the inspect "no such" wording on Podman and nerdctl

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
67/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp, docker
Domain
cli, testing

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:

  1. A run is create then start -a -i: that start -a -i propagates the container's exit code and carries stdin/stdout/stderr, and that create accepts the same isolation flags (--rm, --read-only, --tmpfs, --cap-drop, --security-opt, --memory, --cpus, --pids-limit).
  2. Teardown counts a container as absent only when inspect exits 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

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.

More from jchable/okf4net

All issues in jchable/okf4net

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.