Use docker sdk in testing
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 0
- Forks
- 6
- Avg merge
- 12h 25m
- Merged PRs (30d)
- 5
Description
Currently each call to docker cli is done by creating a new subprocess, this would probably be simpler (and cleaner) to use the docker sdk (which, iirc, directly communicates with the daemon)
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No files, tests, or entry points are named. Start by locating the testing code that creates Docker CLI subprocesses and identify every such call. Compare the available Docker SDK interface, then consider the work complete when the testing paths communicate through the SDK instead of spawning the CLI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100