How did you test whether Trivy vulnerabilities are resolved?

I uploaded the newly build docker image into docker hub and enabled the scout image analysis following this guide(The local docker scout command keeps failing).

Here is a screenshot:

It shows having 1 critical, 31 high, 492 medium, 85 low vulnerabilities.
On contrast, existing image having 14 critical, 138 high vulnerabilities based on the security tab.

For the new image, here is breakdown of the criticial and high vulnerabilities from source layer:

Should we (1) use this PR to add this ubuntu docker file as option for less vulnerabilities then (2) look into individual critical and high? vulnerabilities to see if they can be addressed/replaced?

@wangxiaoyou1993

Can you update the Trivy job in your branch to build the image based on your Dockerfile and run the tests?
Want to make sure these vulnerabilities are resolved: https://github.com/mage-ai/mage-ai/security/code-scanning