run-host mode shows: exhausted (0 IPs). Try rerunning with larger DNS range.

[NonpareilNic]

When using https://hub.docker.com/r/openziti/ziti-host the docker container is attempting to allocate IP addresses.

Exected Behavior
I expected that when I ran the tunneler I wouldn't get an ERROR indicating "ip pool exhausted"

Actual Behavior:
When running the ziti-edge-tunnel in run-host mode, and when specifying a service that has an intercept configuration, a strange erorr is observed:

ERROR tunnel-cbs:ziti_dns.c:122 next_ipv4() DNS ip pool exhausted (0 IPs). Try rerunning with larger DNS range.

Deployment Method: AWS Fargate Service without a Load Balancer:

log-events-viewer-result (2).csv

[sadath-12]

+1

[qrkourier]

This confirms my hypothesis that the Linux tunneler emits a misleading error message about exhausted IP pool when it is functioning strictly as a reverse-proxy (run-host mode) and does not need or use any intercept IP addresses. @scareything