oakctl app run fails with DNS error / "Internet: Unavailable" over Ethernet

OmkarDevadas

Separate from the conversion issue: oakctl app run . (v0.30.1) fails while the device builds the container. It can't pull debian:bookworm-slim from Docker Hub:

$$
Failed to build application container: Image download failed ...
ConnectError("dns error", "failed to lookup address information: Temporary failure in name resolution")
$$

oakctl device info --check_internet:

$$
Internet: Unavailable
Hub Adoption: Unadopted
Device time: Mon Sep 28 05:13:03 +00:00 2026
IP Addresses: 192.168.100.11/24
DNS Servers: Unknown
Gateways: 192.168.100.1
$$

The device is connected over Ethernet, and its clock is correct now (it showed 1970 earlier).

How do I give the device internet access over Ethernet? It has an IP and gateway but no DNS servers. How do I set DNS on the device?
Does the device always need its own internet access to build the container, or is there a way to deploy without it pulling from Docker Hub?

Thanks,
Omkar

Oskar-Luxonis

Hey OmkarDevadas - I see you reported the same DNS error in the PatchCore thread. Please try Filip’s suggestion there: run resolvectl dns eth0 1.1.1.1 on the OAK through SSH or ADB, then check oakctl device info --check_internet and retry the build. If internet is still unavailable, please check whether 192.168.100.1 gives the OAK access to the internet.

oakctl app run . builds on the OAK and pulls the base image from Docker Hub by default. For an offline setup, you can build a .oakapp on an arm64 Linux host and install the file locally. A local registry is another option, but any other build downloads must also be available locally.

Thanks,
Oskar