-
Notifications
You must be signed in to change notification settings - Fork 84
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
[v20.10] Harbor docker-compose.yaml can't access external DNS after upgrade to Docker 20.10 #1164
Comments
We're running the following docker-compose version installed though PyPi:
|
goharbor/harbor#13718 seems to be the same issue. there are some workarounds like explicitly definining dns-servers in daemon.json |
May be related to / same as moby/moby#41819 |
I noticed the issue when Trivy was unable to download its DB. When I manually logged into the container, I verified by using curl that external domains would not resolve, but that I did otherwise have access to the internet via IP's. Interestingly, I just removed |
@cbeley you can use this workaround. |
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>
Expected behavior
Harbor starts up
Actual behavior
Harbor fails to start up due to DNS timeout errors resolving the external database address
Steps to reproduce the behavior
Install Docker 20.10 on Ubuntu 18.04
Download the Harbor installer package from https://github.com/goharbor/harbor/releases/download/v1.10.4/harbor-offline-installer-v1.10.4.tgz
Extract the package into /etc/harbor/habor
Customise the Harbor configuration in /etc/harbor/harbor/harbor.yml to use an external Postgresql database
Run ./install.sh
Run docker-compose up -d
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.)
3-0ubuntu-bionic then the same docker-compose works without issue.The docker-compose.yaml generated by the installer for us looks as follows:
The text was updated successfully, but these errors were encountered: