Skip to content

docs: improve documentation about mirrors #2847

@afdesk

Description

@afdesk

We no longer have the issue, after adding trivy.registry.mirror.index.docker.io: docker-io.example.com to the trivy-operator-trivy-config ConfigMap. At this point this is more of a documentation issue, to add this information in the docs:

| `trivy.registry.mirror.<registry>` | N/A | Mirror for the registry `<registry>`, e.g. `trivy.registry.mirror.index.docker.io: mirror.io` would use `mirror.io` to get images originated from `index.docker.io` |

Something like 'If you wish to mirror docker.io and/or images without a registry defined, add a mirror for index.docker.io, not docker.io' should be enough to prevent future confusion.

Originally posted by @bh-tt in #2671

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions