I use Telepresence OSS in an environment without Internet, but an error is reported when using Telepresence connect

[qq3200341]

Thank you for your reply, but I got an error when using telepresence connect：

node4:/home/006461/telepresence # telepresence connect -n=csc
telepresence connect: error: connector.Connect: failed to connect to root daemon: rpc error: code = DeadlineExceeded desc = context deadline exceeded

See logs for details (8 errors found): "/root/.cache/telepresence/logs/daemon.log"
If you think you have encountered a bug, please run `telepresence gather-logs` and attach the telepresence_logs.zip to your github issue or create a new one: https://github.com/telepresenceio/telepresence/issues/new?template=Bug_report.md .

daemon.log：
2025-04-07 16:08:45.9399 info ---
2025-04-07 16:08:45.9400 info Telepresence daemon v2.20.2 (api v3) starting...
2025-04-07 16:08:45.9401 info PID is 2885
2025-04-07 16:08:45.9401 info
2025-04-07 16:08:45.9409 info daemon/server-grpc : gRPC server started
2025-04-07 16:08:46.3342 info daemon/session : -- Starting new session
2025-04-07 16:08:46.5072 info daemon/session : Connected to OSS Traffic Manager v2.20.2
2025-04-07 16:08:46.5073 info daemon/session : Connected to Manager 2.20.2
2025-04-07 16:08:46.5091 info daemon/session : also-proxy subnets []
2025-04-07 16:08:46.5092 info daemon/session : never-proxy subnets [130.255.6.96/32]
2025-04-07 16:08:46.5092 info daemon/session : allow-conflicting subnets []
2025-04-07 16:08:46.5093 info daemon/session : Configuration reloaded
2025-04-07 16:08:46.5119 info daemon/session/network : also-proxy subnets []
2025-04-07 16:08:46.5119 info daemon/session/network : never-proxy subnets [130.255.6.96/32]
2025-04-07 16:08:46.5120 info daemon/session/network : allow-conflicting subnets [0.0.0.0/0]
2025-04-07 16:08:47.0124 warning daemon/session/network : Manager IP 100.108.11.244 is connectable but not a traffic-manager instance (rpc error: code = DeadlineExceeded desc = received context error while waiting for new LB policy update: context deadline exceeded). Will proxy pods, but this may interfere with your VPN routes.
2025-04-07 16:08:47.5135 info daemon/session/network : Adding service subnet 10.96.0.0/12
2025-04-07 16:08:47.5136 info daemon/session/network : Adding pod subnet 100.66.209.0/24
2025-04-07 16:08:47.5136 info daemon/session/network : Adding pod subnet 100.74.135.0/24
2025-04-07 16:08:47.5136 info daemon/session/network : Adding pod subnet 100.108.11.0/24
2025-04-07 16:08:47.5136 info daemon/session/network : Adding pod subnet 130.255.6.0/24
2025-04-07 16:08:47.5139 info daemon/session/network : Creating routing table with index 775 and priority 32765
2025-04-07 16:08:47.6086 info daemon/session/network : Setting cluster DNS to 100.108.11.244
2025-04-07 16:08:47.6087 info daemon/session/network : Setting cluster domain to "cluster.local."
2025-04-07 16:08:47.6087 info daemon/session/network : Starting Endpoint
2025-04-07 16:08:47.6105 info daemon/metriton : scout report "update_routes" failed: Post "https://metriton.datawire.io/scout": dial tcp: lookup metriton.datawire.io on [::1]:53: read udp [::1]:55455->[::1]:53: read: connection refused
2025-04-07 16:08:47.6804 error daemon/session/network : failed to retrieve route for subnet 10.96.0.0/12:
2025-04-07 16:08:47.6896 error daemon/session/dns/resolved : systemd-resolved is not running
2025-04-07 16:08:47.6897 info daemon/session/dns : Unable to use systemd-resolved, falling back to local server
2025-04-07 16:08:47.6903 info daemon/metriton : scout report "incluster_dns_queries" failed: Post "https://metriton.datawire.io/scout": dial tcp: lookup metriton.datawire.io on [::1]:53: read udp [::1]:38770->[::1]:53: read: connection refused
2025-04-07 16:08:47.6907 error daemon/session : failed to remove subnet 100.66.209.0/24: Link not found
2025-04-07 16:08:47.6909 error daemon/session : failed to remove subnet 100.74.135.0/24: Link not found
2025-04-07 16:08:47.6910 error daemon/session : failed to remove subnet 100.108.11.0/24: Link not found
2025-04-07 16:08:47.6911 error daemon/session : failed to remove subnet 130.255.6.0/24: Link not found
2025-04-07 16:08:47.6912 error daemon/session/dns : goroutine "/daemon/session/dns" exited with error: couldn't determine dns ip from /etc/resolv.conf
2025-04-07 16:08:47.6913 info daemon/session:shutdown_logger : shutting down (gracefully)...
2025-04-07 16:08:47.6914 error daemon/session/agentPods : goroutine "/daemon/session/agentPods" exited with error: rpc error: code = Canceled desc = context canceled
2025-04-07 16:08:47.7282 info daemon/session:shutdown_status : final goroutine statuses:
2025-04-07 16:08:47.7284 info daemon/session:shutdown_status : /daemon/session/agentPods: exited with error
2025-04-07 16:08:47.7284 info daemon/session:shutdown_status : /daemon/session/dns : exited with error
2025-04-07 16:08:47.7284 info daemon/session:shutdown_status : /daemon/session/network : exited
2025-04-07 16:08:47.7284 info daemon/session:shutdown_status : /daemon/session/vif : exited
2025-04-07 16:08:47.7285 info daemon/session : -- Session ended
2025-04-07 16:08:47.7328 error daemon/session : couldn't determine dns ip from /etc/resolv.conf

Originally posted by @qq3200341 in #3842

[thallgren]

Your /etc/resolv.conf file seems to be broken. Please provide more info about your environment. What type of platform are you using? Are you trying to run Telepresence from within a docker container?

[qq3200341]

No content in /etc/resolv.conf.

I used the telepresence binaries directly without running the telepresence into the docker container.

[thallgren]

So I ask again, what platform are you using? What type of OS is this? What version? I've never seen a /etc/resolv.conf without at least a nameserver entry in it.

[qq3200341]

I am using Telepresence on SUSE Linux Enterprise Server 12 SP5 x86.
Since this machine is not connected to the internet, I have not configured any nameserver in /etc/resolv.conf.

[thallgren]

Not being connected to the outside world doesn't mean that you don't need DNS. You'll need a nameserver if you want Telepresence to find services in your cluster.