Sertaç Özercan
Sertaç Özercan
@bobertrublik looks like there are a few merge conflicts, could you ptal when you get a chance? thanks!
@amanycodes can you add an integration test too
@amanycodes look like the CI is failing. is this ready for review?
@explsd copa doesn't depend on docker but rather uses buildkit. If you can run buildkit as a container with podman, it should work as @ashnamehrotra suggested (https://project-copacetic.github.io/copacetic/website/custom-address) `copa patch -i...
Looks like we do run `docker load` [here](https://github.com/project-copacetic/copacetic/blob/56c1294e9f99cafd702d382961c4a29bf80a4011/pkg/patch/patch.go#L308), so even though it can patch using buildkit as a container with podman, it won't be able to load unless we can...
Podman support is added in v0.11
Closing this one as copa provides this functionality with scanner plugins, and they are out of tree by design. We would love for a wiz plugin! If you are interested...
@tamalsaha thanks for the pr! can you run `make vendor manifests` and commit the changes when you get a chance?
Looks like this breaks GK tests (these are informative), we'll need to handle that when we vendor this in.
This is due to patching w/o vuln reports having an additional run step to check if error_log file exists. This does not happen if vuln reports are specified. https://github.com/project-copacetic/copacetic/blob/d785a5cd6813f7fd4c79fcaf96336dfe441111ed/pkg/pkgmgr/rpm.go#L496 since...