-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Unable to download trivy vulnerability DB #14146
Comments
According to the log message There is a DNS issue moby/moby#31960 about the docker daemon. |
it might be worth a shot to try a docker version <20 which do not have that issue |
I changed the /etc/resolv.conf and add a volume:
|
|
seems like the generated docker-compose.yml hardcodes the services to use the |
Thank you for your help and ideas. My current workaround is to add the /etc/resolv.conf as a volume in the
I don't know why, but it wokrs ¯_(ツ)_/¯ |
@bitsf why you closed this issue? Is it really resolved now? I installed Harbor few days ago and went into same issue. And removing |
Unfortunately it doesn't work again and it run into the same error. After i edit the docker-compose.yml, it works for the moment
|
It's introduced by docker dns change(moby/moby#41022), please see #13718 (comment) to get the workaround. And refer to moby/moby#41819 to get some backgrounds. To remove Think about the scenario, harbor core is searching postgres(which is harbor db) on launching, if the host dns is mounted into harbor core and there is a postgres which is reachable in its network. The harbor core will try to connect to the first reachable postgres host, but in some cases, this postgres may not the harbor db container. |
@wy65701436 maby it is not acceptable, but it works! Do you have a reason why it won't work without removeing? Or better, do you have a reason to solv this problem? |
@Lyrwon after I commented all dns_search entries out in the docker-compose.yml I get a So, is there a stable solution for Harbor? As I do not see any, why this has been closed? |
@mk3rnb8 as far as I understood you get the error because you have no permission to use ping, it is a non-root docker container. However, the solution will probably work, because with standard configuration you will instead receive a timeout. @wy65701436 sorry I get and idea but I do not fully understand your point in not removing |
For details, please refer to goharbor#14146 (comment) and docker/for-linux#1164. If who encounter the issue mentioned by goharbor#6031, add the dns_search: . to the releated container. Signed-off-by: Wang Yan <wangyan@vmware.com>
For details, please refer to goharbor#14146 (comment) and docker/for-linux#1164. If anyone encounter the issue mentioned by goharbor#6031, add the dns_search: . to the releated container. Signed-off-by: Wang Yan <wangyan@vmware.com>
For details, please refer to #14146 (comment) and docker/for-linux#1164. If anyone encounter the issue mentioned by #6031, add the dns_search: . to the releated container. Signed-off-by: Wang Yan <wangyan@vmware.com>
For details, please refer to goharbor#14146 (comment) and docker/for-linux#1164. If anyone encounter the issue mentioned by goharbor#6031, add the dns_search: . to the releated container. Signed-off-by: Wang Yan <wangyan@vmware.com> Signed-off-by: Andreas Lindhé <andreas@lindhe.io>
For details, please refer to goharbor#14146 (comment) and docker/for-linux#1164. If anyone encounter the issue mentioned by goharbor#6031, add the dns_search: . to the releated container. Signed-off-by: Wang Yan <wangyan@vmware.com>
For details, please refer to goharbor#14146 (comment) and docker/for-linux#1164. If anyone encounter the issue mentioned by goharbor#6031, add the dns_search: . to the releated container. Signed-off-by: Wang Yan <wangyan@vmware.com>
I tried the same but not working, I am trying with 2.5.0 harbor]# docker exec -it trivy-adapter trivy fs /; |
Hi, i start a new issue with an old problem:
I get this message if i want scan a pushed image with trivy:
I have started harbor on an Ubunut 18.04 VMBox and an Ubuntu 20.04 VMBox, both running on Windows 10.
I have tried the same config on a nativ Ubuntu 18.04 but there is the same problem.
I hope anyone of you can help me
The text was updated successfully, but these errors were encountered: