Assigning a port mapping to an already running Docker container can be a bit tricky since Docker doesn't allow you to modify port configurations directly on an active container. However, with some workarounds, you can achieve similar results. This article will explore the various ways you can assign a new port mapping to an existing Docker container and provide detailed explanations along with practical examples.

Understanding Docker Port Mapping

Port mapping in Docker acts as a bridge between a container on a host and allows access to a containerized application from the outside world. When launching a container, ports can be specified using the -p or --publish flag. The syntax generally follows host_port:container_port where:

• Host Port: The port on the host machine.
• Container Port: The port inside the container that needs exposure.

Traditional Method for Port Mapping

When running a new Docker container, you can specify the ports easily with the run command. For example:

docker run -d -p 8080:80 --name webserver nginx

Here, the command launches an instance of the Nginx web server, mapping port 8080 on the host to port 80 inside the container.

Assigning Port Mapping to Existing Containers

Since Docker doesn't support adding port mappings to running containers directly, you'll have to either restart or recreate the container with the desired configuration. Below are the methods to achieve this:

1. Modifying and Restarting Container

One common solution is to stop the container, commit its state to a new image, and run a new container with the desired port mappings.

Step-by-Step Example:

1. Stop the Container:

    docker stop [container_name or container_id]

1. Commit the Container:
   Committing creates a new image from the existing container's state.

    docker commit [container_name or container_id] new_image_name

1. Run a New Container:
   You can then launch a new container using the newly created image with specified ports.

    docker run -d -p [host_port]:[container_port] new_image_name

2. Using Docker Compose

For containerized applications managed with Docker Compose, updating the docker-compose.yml file to include the desired port mappings and then restarting the services can seamlessly achieve the port exposure.

Example Configuration:

1version: '3'
2services:
3  web:
4    image: nginx
5    ports:
6      - "8080:80"

To apply changes:

docker-compose up -d

3. Utilizing Network Address Translation (NAT)

For scenarios where container restart isn't feasible or downtime should be minimized, using iptables for NAT to redirect traffic can route network traffic effectively.

Example:

iptables -t nat -A PREROUTING -p tcp --dport [host_port] -j REDIRECT --to-port [container_port]

This command routes incoming traffic from the host's port directly to the container's port internally.

Key Considerations

• Downtime: Restarting a container causes temporary downtime.
• Data Persistence: Ensure volumes or data directories are managed appropriately to avoid data loss when recreating containers.
• Networking: Several Docker networking modes might impact port mappings, especially custom bridge networks or host mode.

Summary Table

In conclusion, while Docker doesn't natively support modifying port mappings for running containers, the aforementioned methods provide feasible workarounds to achieve the required port exposure. Whether you are operating with simple standalone containers or using Docker Compose for complex multi-containers, understanding these methods and their trade-offs will optimize your workflow in managing containerized applications efficiently.