Skip to content

Commit bc00da7

Browse files
authored
Updated 02f-Container-Vulnerability-Scanning.md
1 parent 486dd20 commit bc00da7

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

old-versions/V0.1/02f-Container-Vulnerability-Scanning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ As containers become an almost ubiquitous method of packaging and deploying appl
1717
### Where and When to use Container Scanner?
1818
<img align="center" src="/document/assets/images/Dev-process.png">
1919

20-
You can use it at the build phase when you're actually building for instance a Dockerfile and looking at the resulting image that you're creating. Another location to perform container scanning would be when you push a container to the registry or when you pull a container from a registry. However, a good approach is scanning before pushing into a trusted container registry then you can say we have a container registry with a scanned version of all images and for deploying in production you can pull from this trusted container registry. (Plase take look into the following image)
20+
You can use it at the build phase when you're actually building for instance a Dockerfile and looking at the resulting image that you're creating. Another location to perform container scanning would be when you push a container to the registry or when you pull a container from a registry. However, a good approach is scanning before pushing into a trusted container registry then you can say we have a container registry with a scanned version of all images and for deploying in production you can pull from this trusted container registry. (Please take look into the following image)
2121

2222
<img align="center" src="/document/assets/images/container-security-pipeline.png">
2323

0 commit comments

Comments
 (0)