-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select scan socket (containerd, podman, docker) #3049
Comments
This issue is stale because it has been labeled with inactivity. |
We don't have an option for that. What if adding |
@knqyf263 That sounds like a good solution to me |
OK. I'll leave it for contributors for the time being. |
I'm interested in this issue but I haven't used any image clients other than Docker before... |
from @knqyf263 in #4044 (comment): I have an idea about the selection of image sources. We are supposed to implement it in v0.41.0. I suggest allowing users to specify the priority of runtimes.
|
Currently, in
pkg/fanal/image/image.go
, the provided container image will be resolved by first the docker daemon, then podman, then containerd, then remote. It would be helpful if there were some way to configure, from the CLI or a config file, which socket(s) to attempt. The current logic is preferential and somewhat confusing.If there is a place that this can be configured already, it would be helpful to know where -- I didn't find it documented anywhere.
The text was updated successfully, but these errors were encountered: