jfrog / jfrog/jfrog-cli-security
scan container images with podman
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
I would like to use the jfrog-cli to scan my container images with podman instead of docker because i´m running the cli with tekton inside a k8s cluster and there is no docker available. e.g. jf podman scan
The jfrog-cli-full image has podman already included an so it would be nice to have a container image scanning command using podman instead of docker.
Additional context
https://github.com/jfrog/jfrog-ecosystem-integration-env/issues/19
Contributor 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.
Research direction
No files or tests are named in the issue. Start by locating the existing container-image scanning entry point and its Docker dependency, then determine how the requested jf podman scan command should invoke Podman in the jfrog-cli-full image. Done means container images can be scanned through Podman without Docker, including the Tekton and Kubernetes use case described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- cli, devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100