stonezdj(Daojun Zhang)

yes, workaround is update the docker-compose and add the env file

@agill17 Is your s3 storage a customer s3?

@asummers, the user group in the nav doesn't retrieve from LDAP/AD server, they are LDAP group which are sync to Harbor database when user login, the searchWithPaging deosn't impact the...

Verify with Harbor proxy cache, the registry.redhat.io returns schema version is 2 ``` "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json", "schemaVersion": 2 ``` but still get the error in the docker client ``` unsupported manifest...

What is your installation type docker-compose or k8s? If the timeout issue is caused by the LDAP login, then we should hit the same issue both the web UI login...

How long it takes the timeout? exceed 900 seconds? if yes, then we could try to update the timeout setting in common/config/nginx/nginx.conf ``` location /v2/ { proxy_pass http://core/v2/; proxy_set_header Host...

Link to issue https://github.com/goharbor/harbor/issues/16367

Got the same error when run install, and finally found that there is a directory `/hostfs` already exist in the VM, after removed this directory, install script works.

@beniamin current Harbor support to proxy the oci helm, for example, if you push an oci helm to dockerhub, and setup a Harbor instance to proxy it, it works. Note:...

With this feature https://github.com/goharbor/harbor/issues/17512 integrated, The admin user could pause all pending tasks (include scheduler) and stop all the running jobs in the worker pool. it meets the requirement of...