Add FAQ entry wrt. containers

[pombredanne]

Here is a few questions that are relevant. We should add these in an FAQ:

When we were talking about container analysis, can you help me understand the current capability of ScanCode or AboutCode in relation to this scope definition of Docker and Container Analysis:

---

• Q: Can you analyze Dockerfiles?
• A: We have code in https://github.com/aboutcode-org/container-inspector/blob/main/src/container_inspector/dockerfile.py for this ... but this may not be wired in other tools at the moment.
  It can for instance map dockerfile instructions to actual docker image history, https://github.com/aboutcode-org/container-inspector/blob/main/src/container_inspector/dockerfile.py#L204

---

• Q: can you analyze a built image? (Build Docker Image Analysis)
• A: Yes, we do this in ScanCode.io. We have one fairly unique feature to actually account for all files used in all layers

---

• Q: Can you analyze all layers of a running Container?
• A: ScanCode.io scans all layers of images. We can scan all layers of a running container if you save the running Container as an image first. We can also fetch images from registries, local files and technically also from a running Container, say in a local docker ... but this has not yet been tested so far. We do not introspect k8s clusters to analyze the deployed and running images there (yet) and that would be a nice future addition. For now we can instead work on the many images there, save and analyze them.

---

• Q: Can you analyze Docker in Docker?
• A: The input to ScanCode is a local saved image, (docker or OCI). docker in docker support will demand to have access to the saved images (either extracted from the docker images in docker, or mounted in a volume or saved from the docker in the docker image). Once saved we can analyze these alright

[pombredanne]

@porsche-rishisaxena FYI ^