This article describes the issue when one of the dockers cannot access the FortiManager.
config system docker (docker)# set universalconnector enable (docker)# end Pulling universalconnector: registry.fortinet.com/universalconnector/universalconnector:latest Error: error contacting notary server: dial tcp 154.52.26.107:4443: i/o timeout Can't pull universalconnector (Error: error contacting notary server: dial tcp 154.52.26.107:4443: i/o timeout)
Scope
Universal Docker and FortiManager.
Solution
To fix the issue, check the connectivity between FortiManager and Universal docker:
Step 1: Check the DNS connection
show system dns config system DNS set primary 208.91.112.52 execute ping 208.91.112.52 PING 208.91.112.52 (208.91.112.52): 56 data bytes 64 bytes from 208.91.112.52: seq=0 ttl=57 time=0.897 ms 64 bytes from 208.91.112.52: seq=1 ttl=57 time=0.899 ms 64 bytes from 208.91.112.52: seq=2 ttl=57 time=0.810 ms 64 bytes from 208.91.112.52: seq=3 ttl=57 time=0.838 ms --- 208.91.112.52 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 0.810/0.861/0.899 ms
Step 2: Ping the IP Docker
execute ping 154.52.26.107 PING 154.52.26.107 (154.52.26.107): 56 data bytes 64 bytes from 154.52.26.107: seq=0 ttl=48 time=269.103 ms 64 bytes from 154.52.26.107: seq=1 ttl=48 time=268.967 ms 64 bytes from 154.52.26.107: seq=2 ttl=48 time=268.919 ms 64 bytes from 154.52.26.107: seq=3 ttl=48 time=268.957 ms
Step 3: Traceroute the Docker IP
execute traceroute 154.52.26.107 traceroute to 154.52.26.107 (154.52.26.107), 32 hops max, 84 byte packets 1 10.5.100.65 2 ms 2 ms 2 ms 2 10.5.60.95 1 ms 1 ms 1 ms 3 10.5.60.9 2 ms 2 ms 2 ms 4 10.5.60.92 0 ms 0 ms 0 ms 5 10.5.53.1 0 ms 0 ms 0 ms 6 43.225.X.X ............. .............. 23 38.104.251.50 269 ms 269 ms 269 ms 24 154.52.26.96 268 ms 268 ms 269 ms 25 154.52.26.107 268 ms 268 ms 269 ms
If there is no issue related to connectivity, continue to reset the docker as below:
dia docker reset universalconnector
After the reset, run again the docker:
config system docker set universalconnector enable end
The result will appear as below::
Starting dockerd Pulling universalconnector: registry.fortinet.com/universalconnector/universalconnector:latest Pull (1 of 1): registry.fortinet.com/universalconnector/universalconnector:latest@sha256:9c2d793b7d58a96d90be33419bb53a466511a87d5aa38287 80a1142f763e9e6d registry.fortinet.com/universalconnector/universalconnector@sha256:9c2d793b7d58a96d90be33419bb53a466511a87d5aa3828780a1142f763e9e6d: Pull ing from universalconnector/universalconnector f84cab65f19f: Pull complete 946349064626: Pull complete d193d7009e28: Pull complete e447673c7935: Pull complete b0532fa0cde1: Pull complete 7fe1e681e7b2: Pull complete 378d19c5f29b: Pull complete 9ea6f8da38ae: Pull complete 41939890cb4e: Pull complete 11cfef38c693: Pull complete 13a75f58c1ee: Pull complete Digest: sha256:9c2d793b7d58a96d90be33419bb53a466511a87d5aa3828780a1142f763e9e6d Status: Downloaded newer image for registry.fortinet.com/universalconnector/universalconnector@sha256:9c2d793b7d58a96d90be33419bb53a46651 1a87d5aa3828780a1142f763e9e6d Tagging registry.fortinet.com/universalconnector/universalconnector@sha256:9c2d793b7d58a96d90be33419bb53a466511a87d5aa3828780a1142f763e9e 6d as registry.fortinet.com/universalconnector/universalconnector:latest registry.fortinet.com/universalconnector/universalconnector:latest Starting universalconnector Creating network "universalconnector_backend" with the default driver