Custom bridge interface is not showing when check ifconfig

General
1

I have created “mybridge1” which is bridge network, but it supposed to show when execute ifconfig, but it is not showing. please refer below details. Please suggest what could be the reason. Thank you

shyam@DESKTOP-OO7EVK2:~$ docker inspect mybridge1
[
    {
        "Name": "mybridge1",
        "Id": "cbd64af9e03646e28d28ce59dc03756b84f876cbb34e8fe7b48ab11db8e6c8b5",
        "Created": "2024-09-09T13:28:47.936416965Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "172.18.0.0/16",
                    "Gateway": "172.18.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {},
        "Options": {},
        "Labels": {}
    }
]
shyam@DESKTOP-OO7EVK2:~$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.19.118.177  netmask 255.255.240.0  broadcast 172.19.127.255
        inet6 fe80::215:5dff:feb9:d36d  prefixlen 64  scopeid 0x20<link>
        ether 00:15:5d:b9:d3:6d  txqueuelen 1000  (Ethernet)
        RX packets 79632  bytes 106475874 (106.4 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3397  bytes 315147 (315.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 152  bytes 17059 (17.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 152  bytes 17059 (17.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
2

I guess Docker Desktop, so everything is in the VM. You won’t see it where you run the docker commands.

3

But i could access the application when I did with host network.

4

Docker Desktop has a fake host network using some kind of proxies automatically detecting ports. IP addresses in a virtual machine will not be available from the host.

Please, read the “Known lmitations”.