Creating custom bridge networks in Docker - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to create a custom bridge network named 'my_bridge'.

Docker

docker network [1] my_bridge

Drag options to blanks, or click blank then click option'

Astart

Bbuild

Ccreate

Drun

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'docker network run' instead of 'create'.

Using 'docker network build' which is for images, not networks.

The docker network create command is used to create a new network. Here, it creates a custom bridge network named 'my_bridge'.

2fill in blank

medium

Complete the command to list all Docker networks including the custom bridge networks.

Docker

docker network [1]

Drag options to blanks, or click blank then click option'

Aprune

Binspect

Crm

Dls

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'docker network inspect' which shows details of one network only.

Using 'docker network rm' which deletes networks.

The docker network ls command lists all Docker networks, including custom bridge networks.

3fill in blank

hard

Fix the error in the command to create a custom bridge network with a specific subnet.

Docker

docker network create --driver bridge --subnet [1] my_custom_net

Drag options to blanks, or click blank then click option'

A192.168.1.0/24

B192.168.1.256/24

C192.168.1.0/33

D192.168.1.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using an IP with 256 in a segment which is invalid.

Using a mask larger than 32 or missing mask.

The subnet must be a valid CIDR block. '192.168.1.0/24' is correct. The others are invalid IP ranges or missing mask.

4fill in blank

hard

Fill both blanks to create a custom bridge network named 'dev_net' with a gateway IP of 172.18.0.1.

Docker

docker network create --driver [1] --subnet 172.18.0.0/16 --gateway [2] dev_net

Drag options to blanks, or click blank then click option'

Abridge

Bhost

C172.18.0.1

Doverlay

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'host' or 'overlay' as driver for a bridge network.

Putting driver name as gateway IP.

The driver for a custom bridge network is 'bridge'. The gateway IP must be a valid IP address like '172.18.0.1'.

5fill in blank

hard

Fill all three blanks to create a custom bridge network named 'test_net' with subnet 10.10.0.0/16 and gateway 10.10.0.1.

Docker

docker network create --driver [1] --subnet [2] --gateway [3] test_net

Drag options to blanks, or click blank then click option'

Abridge

B10.10.0.0/16

C10.10.0.1

Dhost

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'host' driver instead of 'bridge'.

Using invalid subnet or gateway IP.

Use 'bridge' as the driver for custom bridge networks. The subnet and gateway must be valid IP ranges and addresses.