some docker networks and the swarm can create routing rules that
conflict with the ones we create leading to errors such as:

59:2025-10-15T15:07:33.745853Z  WARN Failed to connect to 10.0.1.243:4000: No route to host (os error 113)
89:2025-10-15T15:08:30.197646Z  WARN Failed to connect to 10.0.1.32:4000: No route to host (os error 113)
92:2025-10-15T15:08:30.837360Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
95:2025-10-15T15:08:33.905356Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
98:2025-10-15T15:08:36.981419Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
101:2025-10-15T15:08:40.049335Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
104:2025-10-15T15:08:43.121680Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
107:2025-10-15T15:08:46.197394Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
110:2025-10-15T15:08:49.265514Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
113:2025-10-15T15:08:52.337454Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
116:2025-10-15T15:08:55.409444Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
119:2025-10-15T15:08:58.481471Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
1