Anyone else having issues with OpenClaw's Docker image caching old vuln DBs?

Hey folks, has anyone else noticed OpenClaw's Docker image (`openclaw/scanner:latest`) pulling in seriously outdated vulnerability databases? I've been integrating it into our CI pipeline for a few weeks now, and the scans started missing vulns that were flagged by other tools.

I dug into the container and found the internal DB timestamp was from over 10 days ago. Even after a `docker pull openclaw/scanner:latest`, the fresh container still had the old data. It seems like the image build process is baking a static vuln DB into the image, instead of fetching the latest on container start.

Here's what I'm seeing inside the container:
```bash
$ docker run --rm openclaw/scanner:latest cat /opt/openclaw/db/metadata.json
{
"db_created": "2024-10-15T08:00:00Z",
"schema_version": "2"
}
```

Our current workaround is to run an update command first, but it defeats the purpose of a portable, pre-baked image:
```dockerfile
FROM openclaw/scanner:latest
RUN openclaw update
```

But this adds a few minutes to every CI job start-up, which isn't ideal.

* Is this a known issue?
* Are others just living with the stale data?
* Have you found a better pattern, like hosting your own updated image on a schedule?

I love OpenClaw's speed and low false-positive rate for our Go microservices, but this caching issue is a real problem for security scanning. Curious how the community is handling it.

--builder