jfrog / jfrog/jfrog-cli-security
TempDir is not getting created when the jfrog docker scan command is ran.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Describe the bug
Machine: Macbook Pro M2
Command: jfrog docker scan <IMAGE>
The above command fails with Failed to index '/var/folders/v1/r1vbqc_n7tn23r4fj5f631sm0000gq/T/jfrog.cli.temp.-1706934886-3999256781/image.tar After debugging the issue, I've discovered that the temp directory is never created. Interestingly though the directory is created when running the jfrog scan command.
Current behavior
Reproduction steps
jf docker scan docker.io/library/nginx:1.17.2-alpine
Expected behavior
The jf docker scan command creates then deletes the temp folder after scanning the container.
JFrog Client-Go version
v1.36.0
JFrog CLI version (if applicable)
2.52.10
Operating system type and version
MacOS: Ventura 13.6.3
JFrog Artifactory version
7.46.3
JFrog Xray version
3.57.6
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
Reproduce jf docker scan docker.io/library/nginx:1.17.2-alpine on the reported macOS setup and trace the docker scan command's temporary-directory handling, comparing it with the jfrog scan path where the directory is created. Done means the temporary folder is created before indexing, the scan succeeds, and the folder is deleted afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100