-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
confused log in clair container #10222
Comments
Same here!
Clair logs here:
|
I found this log in registryctl container when starting
|
hi, same here:
i get to this thread becasue i am still not able pull image to harbor ..still get:
installation went OK, connect to harbor is via https,, but when i create CA and so on, i do not see under systemcl status docker mentioned line with docker/certs..... also on web portal clair shows "unhealthy" status thanks for hints... |
update:
anyway... logs stil looks not good:
and push still do not work: $ docker push harbor-test.xxxx.xx/test/wiki:test |
solved,, turn off proxy or no_proxy in systemd conf... |
@lazzio7 I am having the same problem. I added my domain to the |
for http harbor:
for https harbor.. i had to turn off proxy ... |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closes goharbor#10222 Signed-off-by: He Weiwei <hweiwei@vmware.com>
Closes goharbor#10222 Signed-off-by: He Weiwei <hweiwei@vmware.com>
Closes goharbor#10222 Signed-off-by: He Weiwei <hweiwei@vmware.com>
Closes goharbor#10222 Signed-off-by: He Weiwei <hweiwei@vmware.com> Signed-off-by: Ye Liu <ye.liu@hp.com>
Closes goharbor#10222 Signed-off-by: He Weiwei <hweiwei@vmware.com> Signed-off-by: molinber <bertrand.molin@credit-agricole.net>
Closes goharbor#10222 Signed-off-by: He Weiwei <hweiwei@vmware.com>
There are some confused logs
ls: /harbor_cust_cert: No such file or directory
for clair when it started.Maybe these logs also exist in others containers.
The text was updated successfully, but these errors were encountered: