Docker Volume:

Docker allows you to create something called volumes. Volumes are like separate storage areas that can be accessed by containers. They allow you to store data, like a database, outside the container, so it doesn't get deleted when the container is deleted. You can also mount from the same volume and create more containers having the same data. Volumes have several advantages over bind mounts:

• Volumes are easier to back up or migrate than bind mounts.

• You can manage volumes using Docker CLI commands or the Docker API.

• Volumes work on both Linux and Windows containers.

• Volumes can be more safely shared among multiple containers.

• Volume drivers let you store volumes on remote hosts or cloud providers, to encrypt the contents of volumes, or to add other functionality.

• New volumes can have their content pre-populated by a container.

• Volumes on Docker Desktop have much higher performance than bind mounts from Mac and Windows hosts.

Docker Network:

Docker allows you to create virtual spaces called networks, where you can connect multiple containers (small packages that hold all the necessary files for a specific application to run). This way, the containers can communicate with each other and with the host machine (the computer on which the Docker is installed). When we run a container, it has its own storage space that is only accessible by that specific container. If we want to share that storage space with other containers, we can't do that.

By default, when you create or run a container using docker create or docker run, the container doesn’t expose any of its ports to the outside world. Use the --publish or -p flag to make a port available to services outside of Docker. This creates a firewall rule in the host, mapping a container port to a port on the Docker host to the outside world.