Port Mapping with Docker

Why and how to use port mapping in Docker? An introduction for beginners.

In my experience working with software engineers, I have noticed time and again that the concept of of port mapping with Docker containers is one of the more challenging concepts. The typical problems include:

• Why we need ports in the first place?
• How to configure port numbers for containers?

In this article I will focus on these but also touch briefly on adjacent topics. The incremental approach I will use works quite well in practice and I hope it will work for you, too.

Why do we need Ports?

Assume you have a computer running. This can be physical or virtual. For our exploration it does not matter. That computer (or virtual machine) is connected to an IP network. To uniquely identify the computer on that IP network it has an IP address. This is a number combination such as 172.19.16.1. This is an example. You can find out the IP address of your computer by typing in a terminal

nslookup localhost

This may result in an output similar to the following:

Here the IP address for my computer is listed as 172.19.16.1. Yours may be different. When a different computer on the same IP network wants to talk to your computer it can use that IP address to send packages. The computer receives the packages, processes them, and sends a reply, i.e., packages, to the other computer.