Brady Todhunter

@silvio201 great question! I believe we're currently working on a solution for rocky linux, however I'm going to transfer this issue over to the `anchore-engine` project as the folks maintaining...

@tonkapango Can you give me an example of the custom policy you're using? I'd like to see exactly what is going on. There hasn't been any changes to the way...

Started this process in this branch - https://github.com/anchore/ci-tools/tree/clean_up_output

@tonkapango thanks for the suggestion! I'll look into ways that I might be able to make this happen, it might even be possible without any code changes.

Thanks for the suggestion @Starbeuck! I will start looking into this soon. I think I will have to add new functionality to allow users to specify which reports they want...

@davidmankin I've verified the same issue on my workstation. I'm looking into what is causing that issue. In my test, the policy bundle was still loaded & activated correctly, however...

Upon further inspection, the `Error loading tar component` message is a red herring. The image_vuln_scan.sh script is searching the /anchore-engine directory inside of the inline_scan container (which is where all...

@gubbin I've verified that the inline_scan is having issues with the -b option. Can you include a copy of the policy bundle you're trying to activate? I'm also curious about...

hey @jeff-cook thanks for pointing this issue out! A quick fix is to add `source /opt/rh/rh-python36/enable` before trying to run `anchore_ci_tools.py`. That gets sourced in the docker-entrypoint.sh but it looks...

@jeff-cook I'm working on an update that will hopefully make that step unnecessary. I'll update the issue when it's in.