Hi community members, we are considering to discover the software installed within Docker containers and implement an additional normalize schedule. Here we face some challenges and we are wondering if anyone from the community has additional ideas how to tackle them. Container and container images Since the container instances are deployed and shut down on demand we'd rather focus on the container images as a source for software inventory information. Incorporating every (probably short-lived) container instance into our software inventory doesn't seem to make much sense to us: all instances stemming from the same instance are more or less identical and share the same content. However, data platform cannot properly display the images  because it sticks to the concept of a host computer. We might handle container images as special hosts but are not sure if that works out in the end. Or shall we better manage the individual container instances?  Here we might run into deduping issues if multiple similar containers run on the same host. Inventory The software within the container images will be deployed by various ways. In some cases even preconfigured contaier images (i.e. from dockerhub) might be used. So we don't have real control on how the installations are made, e.g. add/remove software entries don't really exist. We think we have to incorporate a full software scan of the container images to get the full picture. Fortunately enough we've already got an analysis software in place (JFrog XRay) which scans the containers for vulnerabilities and license compliance issues. It lokks as if  this software can also produce a list of all software found in the container image. This list could in turn be imported into data platform.  But will data platform properly recognize the data? We don't really want to enter every software into the private catalog. Has anyone done that already and could share her/his experiences?    Any other ideas? Any other input? Thanks, Stephan ... View more