You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is that if you run docker scan in a folder that has .jfrog/jfrog-apps-config.yml the folder is taken to JAS scan and not the docker container.
Describe the bug
Stumbled when working on #1035
The file was added here that broke our IDEs working on it: https://github.com/jfrog/jfrog-cli/blob/dev/.jfrog/jfrog-apps-config.yml
The issue is that if you run docker scan in a folder that has
.jfrog/jfrog-apps-config.yml
the folder is taken to JAS scan and not the docker container.Current behavior
Take a look at:
https://github.com/jfrog/jfrog-cli-core/blame/dev/xray/commands/audit/jas/common.go#L73
workingDirs
is not taken in to account if the config file exists. In the case of docker scan the current dir is not passed but a docker .tar file.Reproduction steps
Run
jf docker scan [container]
in the jfrog-cli projectExpected behavior
The container should be scanned. AKA the yaml file passed should include the docker tar file
JFrog CLI-Core version
dev
JFrog CLI version (if applicable)
dev
Operating system type and version
OS X 14
JFrog Artifactory version
No response
JFrog Xray version
No response
Workaround
Run in a different folder the docker scan
The text was updated successfully, but these errors were encountered: