Greenbone image registry unreachable

Community Containers
1

# unable to pull gvmd / gvm-tools containers - Kindly help
/etc# docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition pull
[+] Pulling 35/55
:heavy_check_mark: openvas Skipped - Image is already being pulled by configure-openvas 0.0s
:heavy_check_mark: openvasd Skipped - Image is already being pulled by configure-openvas 0.0s
:heavy_check_mark: gpg-data Pulled 4.7s
✘ gvmd Error Get “https :// registry .community.greenbone.net/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exceeded … 15.6s
:heavy_check_mark: redis-server Pulled 4.9s
:heavy_check_mark: dfn-cert-data Pulled 5.1s
⠴ pg-gvm [⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀] Pulling 15.6s
⠴ vulnerability-tests [⠀⠀] Pulling 15.6s
:heavy_check_mark: configure-openvas Pulled 5.2s
✘ gvm-tools Error context canceled 15.6s
:heavy_check_mark: gsa Pulled 5.3s
⠴ cert-bund-data [⠀⠀] Pulling 15.6s
⠴ ospd-openvas [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡀⣿⣿⣿⣿⣿⠀⠀⠀⠀] Pulling 15.6s
⠴ scap-data [⠀⠀] Pulling 15.6s
⠴ notus-data [⣿⠀⠀⠀] Pulling 15.6s
⠴ report-formats [⠀⠀] Pulling 15.6s
:heavy_check_mark: data-objects Pulled 5.3s

Error response from daemon: Get “https :// registry .community.greenbone.net/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

#unable to reach greenbone registry
~# curl -v https :// registry.community.greenbone.net/v2/

  • Trying 45.135.106.145:443…
  • Trying [2a0e:6b40:20:106::feed:145]:443…
  • Immediate connect fail for 2a0e:6b40:20:106::feed:145: Network is unreachable
    ^C
    ~# ping 45.135.106.145
    PING 45.135.106.145 (45.135.106.145) 56(84) bytes of data.
    ^C
    — 45.135.106.145 ping statistics —
    5 packets transmitted, 0 received, 100% packet loss, time 4100ms

#google reachability working fine
root@openvas:~# ping www .google .com
PING www. google. com (142.250.182.228) 56(84) bytes of data.
64 bytes from bom07s29 -in-f4.1e100.net (142.250.182.228): icmp_seq=1 ttl=116 time=6.41 ms
64 bytes from bom07s29 -in-f4.1e100.net (142.250.182.228): icmp_seq=2 ttl=116 time=6.58 ms

even tried with google nameservers but same error:
~# cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.8.4

2

Same issue,

Tried different network, different DNS server, different machines. Noticed yesterday (Aug 5th)
Most likely connected to this report on github.
Cannot fetch gvmd - i/o timeout · Issue #2276 · greenbone/gvmd (github.com)

3

Same issues, I have checked DNS logs and nothing is blocked. Went over DNS servers, pinging them and all. Even checked the A records for the domain and was able to ping them from the server. Yet I cant do docker image pull and pull the image in the docker compose file.

4

+] Running 34/17
✘ gvm-tools Error context canceled 15.4s
⠸ notus-data [⠀⠀⠀] Pulling 15.4s
⠸ report-formats [⠀⠀] Pulling 15.4s
⠸ cert-bund-data [⠀⠀] Pulling 15.4s
✘ gvmd Error Get “https://registry.community.greenbone.net/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exc… 15.4s
⠸ redis-server [⣿⣿⣿] 19.36MB / 20.16MB Pulling 15.4s
⠸ pg-gvm [⣷⣷⣿⠀⠀⠀⠀⠀⠀⠀] Pulling 15.4s
⠸ gsa [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 57.26MB / 58.94MB Pulling 15.4s
⠸ openvasd Pulling 15.4s
⠸ data-objects [⠀⠀] Pulling 15.4s
⠸ configure-openvas [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 114.3MB / 119.4MB Pulling 15.4s
⠸ vulnerability-tests [⠀⠀] Pulling 15.4s
⠸ scap-data [⠀⠀] Pulling 15.4s
⠸ ospd-openvas [⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀] Pulling 15.4s
⠸ dfn-cert-data [⠀⠀] Pulling 15.4s
⠸ openvas Pulling 15.4s
:heavy_check_mark: gpg-data Pulled 2.6s
Error response from daemon: Get “https://registry.community.greenbone.net/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

5

If you need to build the contaiers while Greenbone fixes the route to the new container registries, you can simply remove the registry.community.greenbone.net/community from the altered locations and replace them with greenbone, aka, revert the changes made to the docs so far.

3 Likes
6

Hi @rippledj - thanks - it works immediately!

7

This should be fixed now and registry.community.greenbone.net/community should be reachable now and contain all images of the community containers!

3 Likes