Docker interface showing "Network device is not present"

Installing and Using OpenWrt
1

Hello. I just installed OpenWrt and Docker on NanoPi R6S and here's the issue I'm having:

KqG1CV5
KqG1CV5525×139 10.7 KB

What's interesting is that I already set up one Docker container and I can access it without a problem. So I guess this is just a cosmetic bug in LuCI?

Not sure where to go from there, any help is appreciated.

root@OpenWrt:~# cat /etc/config/network

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd05:ae04:de0d::/48'
        option packet_steering '1'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0'
        list ports 'eth2'

config device
        option name 'eth0'
        option macaddr 'c6:af:f4:6d:60:e8'

config device
        option name 'eth2'
        option macaddr 'c6:af:f4:6d:60:e8'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'

config device
        option name 'eth1'
        option macaddr 'c6:af:f4:6d:60:e7'

config interface 'wan'
        option device 'eth1'
        option proto 'dhcp'
        option peerdns '0'
        list dns '1.1.1.1'
        list dns '1.0.0.1'
        option delegate '0'

config interface 'docker'
        option device 'docker0'
        option proto 'none'
        option auto '1'

config device
        option type 'bridge'
        option name 'docker0'
3

Please post images directly into the forum instead of using 3rd party sites. Additionally, where possible, please use text based configs/logs.

Please use the "Preformatted text </>" button for logs, scripts, configs and general console output (red circle; this works best in the 'Markdown' composer view in the blue oval):

Screenshot 2025-10-20 at 8.14.14 PM

1 Like
4

Thank you, I fixed the post.

5

Do you see docker0 in ip link ?
What is in the /etc/config/network section defining it?

6

Yes, here’s the output:

root@OpenWrt:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br-lan state DOWN qlen 1000
    link/ether c6:af:f4:6d:60:e8 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc cake state UP qlen 1000
    link/ether c6:af:f4:6d:60:e7 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP qlen 1000
    link/ether c6:af:f4:6d:60:e8 brd ff:ff:ff:ff:ff:ff
24: br-9197c854b161: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
    link/ether 02:42:0c:31:ff:10 brd ff:ff:ff:ff:ff:ff
35: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether c6:af:f4:6d:60:e8 brd ff:ff:ff:ff:ff:ff
38: ifb4eth1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc cake state UNKNOWN qlen 32
    link/ether a6:61:45:b3:b8:cc brd ff:ff:ff:ff:ff:ff
40: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
    link/ether 02:42:72:1f:00:3c brd ff:ff:ff:ff:ff:ff

I updated the post with a copy of /etc/config/network, please check.

7

Dunno, add option bridge_empty 1 to docker0, it will ignore absence of backends and be in carrier up state without any container attached.

1 Like
8

What do you mean by absence of backends? Docker is fully configured so I don’t see an issue with my config.

9

Just to get rid of this?

10

@brada4 is right here. Allow the bridge device to be empty.
Which means that currently no interface will be attached to it.
With allow empty, you allow that the bridge is not only there but also in up state.

1 Like