How Do I Assign a Port Mapping to an Existing Docker Container?

When you create a Docker container, you can expose ports using the -p or --publish flag.
For example:

docker run -d -p 8080:80 nginx

Here, port 8080 on the host maps to port 80 inside the container.

But what if you already have a running container and want to assign a new port mapping without recreating it?
Unfortunately, Docker does not support adding port mappings to an existing container directly.

In this guide, we’ll look at why this is the case and the workarounds you can use.

Table of Contents

🔍 Why You Can’t Directly Add a Port Mapping

Port mappings are part of the container’s network configuration, which is set when the container is created. Docker doesn’t allow changing this on the fly because it would require reconfiguring the underlying virtual network interface.

🛠 Workaround 1 – Create a New Container with the Desired Ports

The most common approach:

Find the container’s configuration: docker inspect <container_name>
Stop the container: docker stop <container_name>
Create a new container from the same image with the new port mapping: docker run -d -p 8080:80 <image_name>

You can also use:

docker commit <container_name> my_temp_image
docker run -d -p 8080:80 my_temp_image

This way, the new container will have the same filesystem changes as the old one.

🛠 Workaround 2 – Use Docker’s `--network host` (Linux Only)

If you run the container in the host network:

docker run --network host <image_name>

It will share the host’s network stack, and you can manage ports directly from your host machine.
⚠️ Warning: This bypasses Docker’s port mapping isolation.

🛠 Workaround 3 – Use a Reverse Proxy

If you don’t want to restart the container, you can create a reverse proxy (e.g., Nginx, Traefik, HAProxy) on the host to listen on a new port and forward traffic to the container’s existing port.

Example with socat:

socat TCP-LISTEN:8080,fork TCP:CONTAINER_IP:80

Get CONTAINER_IP with:

docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' <container_name>

📌 Best Practice

If you often change port mappings, define them in a Docker Compose file:

version: "3"
services:
  web:
    image: nginx
    ports:
      - "8080:80"

This makes updates easy—just modify the file and run:

docker-compose up -d

🚀 Final Thoughts

You can’t directly assign a new port mapping to a running Docker container, but recreating the container or using a reverse proxy provides a practical solution. For long-term maintainability, use Docker Compose to manage ports.