This website uses cookies to ensure you get the best experience.
Learn more.
A private container repository contains images used in production. The release process must evaluate known package vulnerabilities without assuming a pushed image is automatically safe. Which approach fits?
Published
- Use only a tag named patched regardless of its image content.
- Treat a successful push as proof that no vulnerabilities exist.
- Use supported image vulnerability scanning and a governed release decision based on relevant findings and artifact identity.
- Delete vulnerability findings before release to make the report clean.
Comments — 0
Sign in to comment