# Container Auto Scan

Container Auto Scan is a Lacework integration that automatically triggers vulnerability assessments for active containers, helping users detect security weaknesses without manual scans. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5464/container-auto-scan

## Description

Container Auto Scan is a Lacework integration that automatically triggers vulnerability assessments for active containers, helping users detect security weaknesses without manual scans.

## Platform availability

Available on 0 of 10 platforms.

## Health score

28/100 (Low), based on 5 of 5 factors.
- Maintained: 0 (last commit 1334 days ago)
- Popular: 28 (23 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Light to run: 20 (8 GB minimum RAM, runs on ARM)
- Security check: 95 (no serious findings, CI, tests)

## Links

- GitHub: https://github.com/lacework-dev/container-auto-scan
- Docker Hub: https://hub.docker.com/r/lacework/container-auto-scan

## Common questions

### How do I authenticate container-auto-scan when running it in Docker?

You can mount the local Lacework CLI configuration file into the container at /home/user/.lacework.toml. Alternatively, pass account, subaccount, API key, and API secret arguments, or use the standard Lacework CLI environment variables.

### Can I force a new scan of containers that were already scanned recently?

By default, containers scanned within the previous day are skipped using a local scan cache. You can override that behavior with the --rescan flag.

### What happens if my container registry is not integrated with Lacework?

The Inline Scanner can fall back and scan active containers that do not have an integrated container registry. It can also pull publicly accessible images through the local Docker daemon.

### How do I tell it to scan only one registry instead of all integrated registries?

By default it enumerates all integrated container registries that can be scanned by Lacework. Use the --registry argument to override that and scan a specific registry.

### How do I change the time window used to find active containers?

The default look-back period for active container repository and tag combinations is one day. You can change it with the --days or --hours arguments.

---
Source: Our Local Host (https://ourlocalhost.com/app/5464/container-auto-scan), the self-hosted and open-source app directory.
