When including container scanning as part of AutoDevOps on a self-managed 17.1.0 server, I consistently get the following errors when gtcs scan is run. I’m not sure what I’m doing wrong:
$ gtcs scan
[INFO] [2024-06-13 13:19:37 +0000] [container-scanning] > Scanning container from registry [container-uri]:c2869b925db4cc4cb9d2f53ae6c404a76d801571 for vulnerabilities with severity level UNKNOWN or higher, with gcs 6.7.3 and Trivy unknown, advisories updated at unknown
[ERROR] [2024-06-13 13:19:37 +0000] [container-scanning] > Scanner has not created a file with results (tmp.json)
[INFO] [2024-06-13 13:19:37 +0000] [container-scanning] > Scan failed. Use `SECURE_LOG_LEVEL=debug` to see more details.
[ERROR] [2024-06-13 13:19:37 +0000] [container-scanning] > 2024-06-13T13:19:37.962Z ERROR The first run cannot skip downloading DB
2024-06-13T13:19:37.962Z FATAL init error: DB error: database error: --skip-update cannot be specified on the first run
What do I need to do to get an initial db down?
Thanks