Docker Desktop: Bridge Network doesn't show up in ipconfig on host

I have three containers that I have assigned to a bridge network in my docker-compose.yml file:

version: '3.8'
networks:
  mybridge:
    name: mybridge
    ipam:
      driver: default
      config:
        - subnet: 172.30.0.0/24
          gateway: 172.30.0.1

I get timeouts from 172.30.0.2 which is set up as:

services:
  web:
    build:
      dockerfile: Dockerfile
      context: ./
    container_name: web
    image: ubuntu-image
    ports:
      - 80:80
      - 443:443
    volumes:
      - ${HOME}/GIT_repository/www/:/var/www/html:rw
      - ${HOME}/GIT_repository/home:/var/www/html/home:rw
      - ${HOME}/GIT_repository/local:/var/local
    networks:
      mybridge:
        ipv4_address: 172.30.0.2

In my ipconfig output, I don’t find an entry for a 172.30.0.0/24 network.

What might I be missing? Could this have something to do with an internal windows firewall?

Note that this bridge network and containers works fine on my linux host.

Thanks,
Ed

That’s because all user defined bridge networks (such as the one in your compose file) are bridged to the docker_gwbridge

   brctl show

Since the containers use a network namespace (think of it as a partition), you will only be able to see the configuration in the container, but not on the host.

Update: my bad. I missed that it’s Docker Desktop. Forget what I wrote as it doesn’t apply to Docker Desktop, as it runs its docker engine in a utility vm. So what I wrote would be still true for the utility vm, but not for your host.