stonezdj(Daojun Zhang)
stonezdj(Daojun Zhang)
The pannic happen when scanning an sbom artifact replicate from dockerhub, because in harbor its type is `IMAGE` and there is no difference with the normal image. and the scanner...
I couldn't reproduce this issue with my env and the same image. `quay.io/argoproj/argocd:v2.6.3` Because harbor proxy rely on HEAD request to link the digest and the tag. If the tag...
Could you please try this `allow all ldap groups below ou=groups,dc=company,dc=local` and change the LDAP group filter option to filter out the unused groups
see https://github.com/goharbor/harbor-arm
The backend API should fallback the not found error in query task to another logic, it could query the scan_report table, if there is a scan_report or vuln in the...
It is an issue in Harbor operator, not in Harbor AFAIK, the instance should be inside the AWS cloud. If the Harbor is installed in EC2 VM with docker-compose, you...
@njucjc could you please share us an account to verify the PR in the Slack
Could you please upload the core.log when the issue occur?
> Yes. (Sorry I missed this.) Scanning should not update pull time. We should consider adding "Last scan time" field if enough people think it is useful. Should we display...
From the server side(harbor-core), it is not easy to check if the current scan is success or fail.