Skip to content

Document metadata.json no such file or directory error

Elif Munn requested to merge docs-container-scanning-tmp-volume into master

What does this MR do?

When scanning with trivy image, if the runner has a volume mount for the /tmp directory, job fails with below error. This is because trivy database is extracted at runtime from /tmp directory. If runner is configured to mount host /tmp directory into the container, below error is received because file compressed database file isn't there anymore.

Failed to get DB metadata	{"error": "unable to open a file: open /home/gitlab/.cache/trivy/ee/db/metadata.json: no such file or directory", "errorVerbose": "unable to open a file:\n    github.com/aquasecurity/trivy-db/pkg/metadata.Client.Get\n        /home/runner/go/pkg/mod/github.com/aquasecurity/trivy-db@v0.0.0-20231005141211-4fc651f7ac8d/pkg/metadata/metadata.go:46\n  - open /home/gitlab/.cache/trivy/ee/db/metadata.json: no such file or directory"}

Related issues

Support ticket - internal only

Author's checklist

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • Ensure a release milestone is set.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

Merge request reports