Revert "refactor(setup-db): to run trivy in docker (#54)" (#56)

This reverts commit 81eda53a59.

Reviewed-on: #56
Co-authored-by: Timo Behrendt <t.behrendt@t00n.de>
Co-committed-by: Timo Behrendt <t.behrendt@t00n.de>

setup-db/README.md

@@ -2,9 +2,7 @@
 
 A reusable Gitea Action that sets up the Trivy vulnerability database, restoring from cache if available.
 
-The action runs Trivy inside **Docker** with a restricted container configuration so the Trivy runtime is isolated from the host while the database is downloaded into your cache directory.
-
-**Note:** This action only prepares the vulnerability database. If you run Trivy on the runner host for scans (for example `trivy fs .`), install Trivy separately (e.g. with a `setup-trivy` action or your own step).
+**Note:** This action only sets up the database. Trivy itself must be installed separately (e.g., using the `setup-trivy` action).
 
 ## Usage
 
@@ -38,9 +36,6 @@ jobs:
 
 ## Inputs
 
-| Input            | Description                                                                 | Required | Default |
-| ---------------- | --------------------------------------------------------------------------- | -------- | ------- |
-| `cache-dir`      | Path to the Trivy cache directory                                           | No       | `${{ runner.temp }}/trivy` |
-| `trivy-version`  | Docker image reference for Trivy (digest pin recommended)                   | No       | Pinned `ghcr.io/aquasecurity/trivy` image in `action.yaml` |
-
-**`trivy-version` is optional.** If you omit it, the action uses the default image (version and digest) from `action.yaml`. Set it only when you need a different Trivy image or your own digest pin.
+| Input       | Description                       | Required | Default          |
+| ----------- | --------------------------------- | -------- | ---------------- |
+| `cache-dir` | Path to the Trivy cache directory | No       | `~/.cache/trivy` |