stonezdj(Daojun Zhang)
stonezdj(Daojun Zhang)
It is possible that the pull event replication is triggered before the tag is set on proxycache. then the replication replicates the artifact with digest.
There are similar issues open https://github.com/goharbor/harbor/issues/15591, it is the behavior of docker/containerd, it cache the tag digest relationship in the local, if there is a cache in the local, it...
It seems that the name of job_logger is invalid, see the sample configure, only support "FILE" and "STD_OUTPUT" ``` job_loggers: - name: "STD_OUTPUT" # logger backend name, only support "FILE"...
The error code 200 means ErrorNetwork, is there any connectivity issue between the LDAP server and harbor ? If you uncheck the "LDAP Verify Certificate" option, then it is not...
The REST API should be sorted by the most matched result
@qnetter should we consider to fix it?
In audit log ``` 29,1,pull,artifact,library/busybox:sha256:0dc78806f5885db569f7389b0e0df2e190346b0df59937268c5862d5bfc5f933,robot$library+Trivy-8c20ae69-f5c1-11ec-8fba-0242ac1e0009,2022-06-27 02:33:43.721128 ``` The robot account name has this pattern start with `robot$` and contains a `+Trivy`. it works for trivy scanner.
Yes, Init the redis works after the if else block of run mode
Does it work in your env? @nknkgithub
Harbor proxy cache support GCR as a registry, you don't have to configure it as a docker registry. what is the core.log of the harbor?